Not a customer? Click the 'Start a free trial' link to begin a 30-day SaaS trial of our product and to join our community.
Existing Cisco AppDynamics customers should click the 'Sign In' button to authenticate to access the community
on 02-03-2022 08:36 PM - edited on 09-17-2024 10:29 AM by Ryan.Paredez
We highly recommend the following standard naming conventions for different configuration items used in AppDynamics because sound naming standards are an important practice for:
|
|
plus more...!
NOTE | In this article, we are specifying standards for setting configuration items' values, rather than methods. See more below.
These recommendations are based on standard configurations and are not intended to be a universal solution, and therefore may not work with custom-configured instances.
Successful naming is based on emphasizing the use of common standards. So, where available, use nomenclature that already exists, whether public or company-based. The following table contains naming best practices for AppDynamics Database Collectors.
Some configuration items do not specify a strict pattern or convention. Instead, we leave it up to you to decide. In such cases the following principle should always apply:
Names chosen for any configuration item should be a sensible, non-technical description.
DO THIS |
NOT THIS |
Use plain language |
Avoid too-formal, distancing language |
Be descriptive, but concise |
Don’t be verbose—or curt |
Use business terminology where possible |
Don’t use technical terms |
Make it meaningful to all intended users |
Avoid jargon that won’t be familiar to all of the intended users. |
PLEASE NOTE: In this article, we are not specifying the method of setting values for configuration items, only standards for the values themselves. In the case of agent configuration properties, use one of the following methods to set the values:
Let us know in the comments below if you have further questions on methods.
Thank you! Your submission has been received!
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form