> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/continuous-delivery/troubleshooting-and-resources/armory/general/settings-for-sysdig-monitoring-of-spinnaker.md).

# Settings for SysDig Monitoring of Spinnaker

### Introduction <a href="#introduction" id="introduction"></a>

When using SysDig, which is using Prometheus under the hood, for monitoring of Armory Spinnaker, there are a number of settings that need to be set to inform the SysDig agent how to communicate with the metrics endpoints of the services.

### Prerequisites <a href="#prerequisites" id="prerequisites"></a>

N/A

### Instructions <a href="#instructions" id="instructions"></a>

After enabling Prometheus type monitoring (metrics stores), add these annotations to **each service** in the **service-settings** section/files: prometheus.io/scrape: 'true' prometheus.io/path: '/prometheus\_metrics' prometheus.io/port: 8008 These annotations should be applied to the pod annotations value in the service-settings for each service to be monitored per <https://spinnaker.io/reference/halyard/custom/#podannotations-podlabels-and-servicelabels>This would result in a **service-settings** section/file similar to the following: kubernetes: podAnnotations: prometheus.io/scrape: 'true' prometheus.io/path: '/prometheus\_metrics' prometheus.io/port: 8008