# Verify Your Microservice With AI

1. Click on Microservices on the left sidebar

<figure><img src="/files/126kSC5aGlT2KmE5XSIs" alt=""><figcaption></figcaption></figure>

2. Selecting Microservices will redirect you to the new modal page where you can click on the + New Microservice button which is in the top right corner

<figure><img src="/files/hiavaEv0ahDGetqQjlC9" alt=""><figcaption></figcaption></figure>

3. Fill out the Microservice **General Details** and **Service Details**

<figure><img src="/files/P7DtWAWyzwRARb29r7nx" alt=""><figcaption></figcaption></figure>

4. Click on Next Step and to Enable Deployment Verification for this Microservice Select the *Environment*, *Enable Auto Rollback,* and set the *Algorithm Aggression*\
   \
   The Auto Rollback Enable allows for the pipeline to be rolled back in case of a failure during the Deployment verification stage.\
   \
   The Algorithm Aggression is a scale that defines the deployment verification aggression for this microservice. It sets the threshold for the severity of the alerts which are to be raised for this microservice.<br>

<figure><img src="/files/oWo0cRwVpoRRYXZZQ2XS" alt=""><figcaption></figcaption></figure>

5. Set up a existing APM provider or create a New one for APM Data ingestion

<figure><img src="/files/DpjPFRDnNZ6E8LCZ6zus" alt=""><figcaption></figcaption></figure>

&#x20;   a)  Create a **New Integration**<br>

<figure><img src="/files/dn4wnDq4Eju1HRGCp1yy" alt=""><figcaption></figcaption></figure>

b) Set up **APM instance** for Deployment Verification\ <br>

<figure><img src="/files/M6UUEM05wn5NXNEKWPpg" alt=""><figcaption></figcaption></figure>

5\) Microservice with Deployment Verification is set up.

The Microservice has been created with Deployment Verification Setup. Upon running a pipeline or a release, the monitoring of various datasources such as Logs Data, Kubernetes Events, Metrics Data and APM data is enabled.<br>

<figure><img src="/files/k49xc6h2a2C7PrtPoOCf" alt=""><figcaption></figcaption></figure>

6\) For a particular microservice under the **Deployment Verification** tab the detected anomalies are listed.<br>

<figure><img src="/files/4LVHp8mAnsLUAfnKERVp" alt=""><figcaption></figcaption></figure>

a) Upon clicking on an anomaly a more detailed view of anomaly is available :\
\
\&#xNAN;*Events Anomaly* :

<figure><img src="/files/oVq0Fj3boI2dxS7cLdte" alt=""><figcaption></figcaption></figure>

*Metrics Anomaly* :

<figure><img src="/files/LrqwXy4PNst3gAvayEcS" alt=""><figcaption></figcaption></figure>

Logs Anomaly:\
\
\ <br>

<figure><img src="/files/EwXFGfn8OjmH9RaLipyb" alt=""><figcaption></figcaption></figure>

APM Anamoly:<br>

<figure><img src="/files/Hpo8ZifIJbkKzyic3MTN" alt=""><figcaption></figcaption></figure>

1. Resolve : Marks the issue as resolved
2. Relevant : Marks Anomalies as relevant
3. Dismiss : Dismiss issues which are not relevant

<figure><img src="/files/MJ5NysgMQW8IZ50VccV4" alt=""><figcaption></figcaption></figure>

\ <br>


---

# Agent Instructions: 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://docs.ozone.one/ozone-end-user-guide/documentation/ci-cd/verify-your-microservice-with-ai.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.