dT .NET batch job monitoring deployment sizing
Hi All,
Need information / help regarding how to size dT session storage and server requirement for batch job monitoring.
For a customer dynaTrace is already deployed for online applications and now they want to monitor batch jobs also.
They got almost 500 batch jobs running throughout the week with long running batch jobs during weekends. So customer is asking what can be the size of session storage for monitoring these many batch jobs.
Is there any best practice or method of hardware requirement for batch job monitoring, what parameters to look for while sizing ?
(Say assume we have a batch job which process 1 million records and can take up to 1 hour)
Note: I have recommended about checking batch jobs first in test environment and come up with sizing but no help from customer.
-Thanks,
Ankur
Hi Herwig,
As of now no meaningful test for batch jobs and that's the issue.
Client has mentioned that they have about 500 batch jobs and wants to know upfront in production what can be approx hardware sizing if a batch job processes 1 million or 2 million records at a time. (They are assuming that the way we size for online applications same is applicable for batch monitoring, which in not the case ).
I have suggested to customer that it may be impractical to monitor all jobs and choose most important ones. Have session storage for maximum 2-3 days...
So, I am looking for what sizing and approach used by other clients who are monitoring batch jobs or any recommendation, which can give us some rough idea about sizing required.
-Thanks
Ankur
Hi Ankur,
most important parameters are the number of request + size (==pure path length). Do you have a test installation with meaningful batch jobs running? If so you can use that one to get a better estimation for the helpful numbers.
regards
Herwig
