Application coding standards/best practices that work well with DynaTrace
Hi
Is there a recommended application coding standards/best practices so that the application can be monitored better using DynaTrace?.
i'm referring to certain Non-Functional Requirements that will make monitoring using DT easier.
Listing down few that we think are good coding practices
- Include Referrer in all request headers so that it is easier to generalize and report the metrics from a back-end shared service.
- Use standard methods for web service definitions. (helps in detecting web methods by the Web Services sensors)
instead of we try to figure out the bets practices on our own we thought it would be good to check if there is some information of that kind already out there.
-Sreerag
I recomend the instrumentation of Interfaces, since the interfaces *should* be less likely to change method signatures.
Alternatively you could use Sensor Annotation. Annotated methods will always be captured by dynaTrace, independent of the method sensors.
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
October 2017
Announcing Dynatrace's Community Member of the Month for October 2017, Ram S.! Click here to read more! 