Re: Performance Monitoring
Date: Mon, 22 Aug 2022 00:00:57 -0400
Message-Id: <0823DE76-3991-4505-BA9E-3D13F2D7DC3C_at_gmail.com>
We use both products for a very large Oltp app . I would not encourage removing OEM in favor of dynatrace as they come from opposite sides of the problem. Dynatrace is a bit more focused on the app side , and does not have as robust amount of features as OEM . Dynatrace is also more resource intensive than OEM - plan on about 2 full cpu just for the dynatrace agents on the host , while OEM maybe .25 to .75 cpu . You need a small to medium db server and a small app server for OEM while dynatrace needs about 4 cpu for just the app server . The project uses at least 2000 cpu on 2-4 node RAC configs .
That said - dynatrace and OEM agents live happily together on the same server , and the licensing is actually cheaper for OEM . We had this same issue picking Dynatrace or OEM - DBA’s will not be happy with just dynatrace , so we use both . Also for anybody considering Dynatrace , also look at New Relic : all the projects I have worked on have had 100% positive feedback on New Relic . We consider them equally good products . Also - you will probably retain the Diag and Perf packs for Oracle , in which case turns OEM into a very low cost monitoring tool compared to Dynatrace .
Long story short - do not pick one over the other - use both !!
Sent from my Atari 2600
> On Aug 21, 2022, at 1:37 PM, Pap <oracle.developer35_at_gmail.com> wrote:
>
>
> I have not used dynatrace extensively though but seen dynatrace used mainly monitoring aspect across many other app tools but not just databases. And as per my understanding the dynatrace agent has to be installed in the respective hosts which you are going to monitor.I have seen long running sqls list and their execution count and the services they are coming from, but not seens anytime attaching profile/baselines through this tool which you may be using to do it through OEM. Also I have not seen the IO trends(big read vs small read response etc) for the storage cells for exadata machines in dynatrace. Others may comment.
>
> There are many comparisons available between these two on the internet if you google it, But yes , you may need to be aware of all the CONS of the dynatrace before moving away from OEM.
>
>> On Sat, Aug 20, 2022 at 4:17 PM Lok P <loknath.73_at_gmail.com> wrote:
>> Hello , We are managing a third party database(mostly performance font) and we are currently using OEM for debugging and monitoring Oracle database wait events , sql plan , sql monitor , object statistics, Database host IO CPU, Memory etc, exadata storage cell level stats like , Cell IO/CPU/Memory trends also we have configured multiple alerts in OEM.
>>
>> We are getting push from the team, if the same work can be done through dynatrace tool without access to OEM. So I want to understand from experts here if anybody has used a dynatrace tool for database monitoring and analysis work, and how is the experience? And does the dynatrace agent have to be installed in all the DB nodes and Storage cell nodes too?
>>
>> https://www.dynatrace.com/news/blog/intelligent-observability-for-oracle-and-sql-databases/
>>
>> Regards
>>
>> Lok
-- http://www.freelists.org/webpage/oracle-lReceived on Mon Aug 22 2022 - 06:00:57 CEST