can anyone check out whether it is possible for dt to support the following environment?
Net Framework 4.0
1)Exchange 2013
2)Lync 2013
3)Office Web Service 2013
4) SPS 2013
Hi Kim
dynaTrace does support .NET 4.0 - for more details check out the dynaTrace 5.6 Release Notes
Hi Grabner,
Thanks for your update. I knew that dt supports .NET 4.0. I would like to see whether the following products can be supported by dt.
unfortunately, I can' find anything in the dynaTrace 5.6 Release Notes.
1)Exchange 2013
2)Lync 2013
3)Office Web Service 2013
4) SPS 2013
Hi Kim
Well - the question is what level of support you want? Do you want to add a dynaTrace Agent to Lync and expect to see all Lync Messages and Voice Calls over it? Then the answer is probably no because Lync might not be fully implemented in .NET + the communication protocols used might be propriatory and with that you wont get out-of-the-box End-to-End Tracing.
Same is probably true for Exchange. If you expect to see all internal message processing in Exchange then the answer is most likely no.
dynaTrace can monitor applications based on .NET. If there are .NET components in these 4 listed products it is possible to you get to see certain transactions recorded. However - knowing that these products have been out there for a while I assume they are not purely .NET but contain a lot of legacy and native components. Thats why you probably wont see every individual transaction end-to-end captured as a PurePath.
For Exchange and Lync you may want to look into DCRUM. DCRUM is able to analyze network traffic and is able to do some decoding on Exchange and Lync.
Andi
Hi Andi,
Correct. This is what i want. the customer wants to use dt to monitor thier evironment,
they need me to let them know if they can be fully supported.
Thanks,
Sanghyun Kim
Welcome the
Dynatrace Community Forums
Check out the Forum User Guide and Forum Guidelines to learn how to get started.Community Member of the Month
August 2017
Announcing Dynatrace's Community Member of the Month for August 2017, Rick B.! Click here to read more! 