> For the complete documentation index, see [llms.txt](https://gia-duong-duc-minh.gitbook.io/notes/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gia-duong-duc-minh.gitbook.io/notes/computer/microservices/log-deployments-and-changes.md).

# Log deployments and changes

## Context

You have applied the \[\[Microservice architecture]] pattern.

## Problem

How to understand the behavior of an application and troubleshoot problems?

## Forces

It useful to see when deployments and other changes occur since issues usually occur immediately after a change

## Solution

Log every deployment and every change to the (production) environment.

## Examples

A deployment tool can, for example, publish a [pseudo-metric](/notes/computer/microservices/application-metrics.md) whenever it deploys a new version of a service. This metric can then be displayed alongside other metrics enabling changes in application behavior to be correlated with deployments. See [Tracking Every Release by Mike Brittain](https://codeascraft.com/2010/12/08/track-every-release/)

AWS Cloud Trail provides logs of AWS API calls.

## Resulting Context

This pattern has the following benefits:

* Enables deployments and changes to be easily correlated with issues leading to faster resolution.

## Related patterns


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://gia-duong-duc-minh.gitbook.io/notes/computer/microservices/log-deployments-and-changes.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.