• Forums
    • Public Forums
      • Community Connect
      • Dynatrace
        • Dynatrace Open Q&A
      • Application Monitoring & UEM
        • AppMon & UEM Open Q&A
      • Network Application Monitoring
        • NAM Open Q&A
  • Home /
  • Public Forums /
  • Application Monitoring & UEM /
  • AppMon & UEM Open Q&A /
avatar image
Question by Steven L. · Feb 19, 2014 at 10:25 AM ·

Dynatrace hardware configuration

 

Hello,

I have a question about the hardware specs for Compuware APM,

If the information Is present on the website, I apologize, I aim a new user and I could not directly find it.

 

This are the specs we obtained by a Compuware consultant about hardware needs,

 

Question

My boss was a little bit stressed out about the data retention (1,68TByte / day),

I think he is seeing this as database space (expensive),

I remember ChrisG. says that Compuware saves some data on the disk and other data into the database,

 

Is this correct? What data is saved into the database? And what data on disk?

I made a simple hardware config (in attach), my boss likes schemas (smile), is this correct?

 

1.1         dynaTrace Server

, the following hardware is required:

  • 64-bit Windows Server,8+ CPU Cores,16+ GB RAM

This will hold :

  • dynaTrace server (6GB Heap),1 or 2 dynaTrace Collectors (2GB Heap),dynaTrace Analysis Server (4GB Heap)

 

1.2         Data Retention

If the customer wants to store all the sessions at sustained peak levels of 50000 transactions per minute, then about 1,65TB storage per day of retention will be required. For three weeks this amounts to 35 TB of storage requirements.

It is possible the the customer will use a ramp-up period, and start the implementation with a lower number of transactions, and for shorter periods of time.

1.3         dynaTrace Collector

 

To reduce firewall overhead and delays during agent startup; a collector machine is recommended. If the customer chooses not to install this separate server, then certainly 2 collector processes will need to be installed on the dynaTrace server to handle the load of all 35 agents.

  • 64-bit Windows Server,2+ CPU Cores,4+ GB RAM

This will hold :

  • dynaTrace Collector (2GB Heap)

1.4         Database server

The database engine will be installed on a separate machine, and is best sized by DBAs. The Performance Warehouse Database size can grow to 16GB of data.

Comment

People who like this

0 Show 0
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

2 Replies

  • Sort: 
  • Most voted
  • Newest
  • Oldest
avatar image
Best Answer

Answer by Andreas G. · Feb 20, 2014 at 09:41 AM

Hi Steven

I actually used your schema in yesterdays Community Webinar to explain what type of storage we use. There is basically two types of data we store

a) PurePaths -> all these transactions that we capture end - to - end

b) Time Series Data -> these are all the measures such as Response Time, CPU, Memory, ... -> the stuff you put on a dashboard or that you use for alerting.

 

PurePaths are stored on the file system. This is what you configure in Server Settings -> Storage. We called it "Continuous Session" because we continously store new incoming PurePaths on disk until we fill up the quota. If the quota is full we remove old PurePaths. Depending on your PurePath volume (how many you have per hour, day, ...) it can mean that 1TB of storage gives you 1 day of PurePaths or 1 week. The more storage the longer back in time you can look AT EVERY PurePath that has been recorded

Time Series Data is stored in a database. WE also call it Performance Warehouse configured through Server Settings -> Performance Warehouse. We store Time Series data with a 1 min aggregation but then also "age" data, e.g: after 2 weeks we aggregate it to 1 hour, ... -> this can also be configured in that configuration dialog.

I hope this makes sense.

Comment

People who like this

0 Show 0 · Share
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

avatar image

Answer by Steven S. · Feb 20, 2014 at 04:25 PM

It would also help to have a short discussion for those users who also deploy SILK PERFORMER why one gets the informational error to turn off "continuous session" recording when using a load test - too much data being captured with multiple VU's??

Comment

People who like this

0 Show 1 · Share
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

avatar image Andreas G. ♦ · Feb 20, 2014 at 05:14 PM 0
Share

The reason why this is recommended is because SilkPerformer has a feature to "Start REcording" a new session. That means - when you start a SilkPerformner Load Test Silk will tell dynaTrace to start a new session recording (this will only work if Cont Session is turned off). Then it runs the Load Tests and all these PurePaths end up in that stored session. At the end Silk is stopping session recording again. The result is that you have a recorded session for each Load Test.

BUT - you can also use Cont. Session Recording. No problem with that at all. The PurePaths will still be there in the Continuous Session and you can - if you want to keep these results per load test always do a "Store Session" for a certain timeframe.

How to get started

First steps in the forum
Read Community User Guide
Best practices of using forum

NAM 2019 SP5 is available


Check the RHEL support added in the latest NAM service pack.

Learn more

LIVE WEBINAR

"Performance Clinic - Monitoring as a Self Service with Dynatrace"


JANUARY 15, 3:00 PM GMT / 10:00 AM ET

Register here

Follow this Question

Answers Answers and Comments

2 People are following this question.

avatar image avatar image

Forum Tags

dotnet mobile monitoring load iis 6.5 kubernetes mainframe rest api dashboard framework 7.0 appmon 7 health monitoring adk log monitoring services auto-detection uem webserver test automation license web performance monitoring ios nam probe collector migration mq web services knowledge sharing reports window java hybris javascript appmon sensors good to know extensions search 6.3+ server documentation easytravel web dashboard kibana system profile purelytics docker splunk 6.1 process groups account 7.2 rest dynatrace saas spa guardian appmon administration production user actions postgresql upgrade oneagent measures security Dynatrace Managed transactionflow technologies diagnostics user session monitoring unique users continuous delivery sharing configuration alerting NGINX splitting business transaction client 6.3 installation database scheduler apache mobileapp RUM php dashlet azure purepath agent 7.1 appmonsaas messagebroker nodejs 6.2 android sensor performance warehouse
  • Forums
  • Public Forums
    • Community Connect
    • Dynatrace
      • Dynatrace Open Q&A
    • Application Monitoring & UEM
      • AppMon & UEM Open Q&A
    • Network Application Monitoring
      • NAM Open Q&A