Observability - Convention v/s Configuration

Author
Alaa Al Marayat

A common problem our customers face is the planning, organisation and maintenance of configuration. Observability vendors have explored and implemented several techniques to try and elevate the problem.

This brief note is about the benefits that Attuned Technology has seen from the user of convention versus configuration. This complexity management strategy has been used by developers for over a decade now, yet we find that Observability environments have fallen behind in its adoption.

Convention v/s configuration enforces the need to forward plan and think about our Observability configuration holistically. We take into consideration all the stakeholders, present and future relevance of naming standards and various downstream systems that could interact and be impacted by the configuration related data they receive.

The coding and complexity of configuration management tools like Terraform, downstream systems like MuleSoft/Ingnio/ServiceNow and notification recipients like email templates, slack channel and MS Teams are greatly simplified with the use of  conventions.

Attuned Technology has championed the use of conventions. We advise and work with our customers and their partners/vendors to ensure the smooth adoption and longevity of the Observability platform.

Our experience in implementing robust, flexible, fit-for-purpose, mature and scalable Observability makes us the right choice for your organisation.

Author
Written By
Alaa Al Marayat

None