cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Claudia.Landivar
AppDynamics Team (Retired)

What naming conventions are recommended when defining configuration objects in AppDynamics Dashboards?

 

We highly recommend the following standard naming conventions for different configuration items used in AppDynamics because sound naming standards are an important practice for:

  • Efficient identification of objects
  • Understanding data context
  • Navigation
  • Searching
  • Housekeeping
  • Decommissioning efforts

plus more...!

 

NOTEIn 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. 

 

In this article...


 

Naming conventions for AppDynamics Dashboards

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 Dashboards.

 

Dashboard naming conventions

{Team who owns the Dashboard}_{Full Business Application Name or Service}_{Dashboard Purpose}

Example: CoE_MCA_ExecutiveSummary

Since Dashboards do not have any hierarchy, the dashboard name must be used to segregate the dashboards into logical groups.

Back to Contents

 

Overarching principles for naming conventions

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.
When in doubt, leave it out.

 

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:

  • Configuration files
  • System Properties
  • Environment Variables

Let us know in the comments below if you have further questions on methods.

Back to Contents


 

Additional Resources

 

Need to go deeper? Reach out to Call a Consultant

Version history
Last update:
‎02-03-2022 09:11 PM
Updated by:
June 26 Webinar
Discover new Splunk integrations and AI innovations for Cisco AppDynamics.


Register Now!

Observe and Explore
Dive into our Community Blog for the Latest Insights and Updates!


Read the blog here