assess-observability

Defining an observability strategy requires assessing monitoring, logging, and tracing needs based on project context. This Skill evaluates your infrastructure and proposes suitable platforms while updating your adoption file with the chosen strategy.

Choosing monitoring and tracing platforms involves comparing tools against observability principles and best practices. This Skill follows a resolution cascade referencing guidelines to propose suitable solutions for your specific architecture, such as a microservices-based setup.

Documenting observability decisions as an ADR requires recording the selected monitoring, logging, and tracing choices. This Skill creates an Architecture Decision Record or Log to formalize your observability strategy and automatically updates your infrastructure.md file.

Yes, this observability strategy assessment works for microservices architecture. It evaluates the specific monitoring, logging, and tracing needs of distributed systems and guides you through selecting and configuring appropriate platforms for effective debugging.

Setting up logging and tracing requires an evaluation of your current infrastructure and adherence to observability principles. This Skill assesses your project context to recommend appropriate platforms and configuration approaches for effective system monitoring.