> For the complete documentation index, see [llms.txt](https://docs.ozone.one/ozone-end-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ozone.one/ozone-end-user-guide/documentation/ci-cd/verify-your-microservice-with-ai.md).
# Verify Your Microservice With AI
1. Click on Microservices on the left sidebar
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
3. Fill out the Microservice **General Details** and **Service Details**
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.
5. Set up a existing APM provider or create a New one for APM Data ingestion
a) Create a **New Integration**
b) Set up **APM instance** for Deployment Verification\
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.
6\) For a particular microservice under the **Deployment Verification** tab the detected anomalies are listed.
a) Upon clicking on an anomaly a more detailed view of anomaly is available :\
\
\&#xNAN;*Events Anomaly* :
*Metrics Anomaly* :
Logs Anomaly:\
\
\
APM Anamoly:
1. Resolve : Marks the issue as resolved
2. Relevant : Marks Anomalies as relevant
3. Dismiss : Dismiss issues which are not relevant
\