Observability Plugin
Observability Plugin is used to pull metrics directly from Spinnaker microservices. This plugin increases performance, reduces system load, and provides additional features such as metric filtering.
The Observability plugin works in two key ways:
It enables customizing the Micrometer registry.
It exposes an OpenMetrics endpoint for the Micrometer/Spectator metrics, allowing tools such as Prometheus or platforms that query open metrics formats to work without needing a sidecar.
These allow for key improvements in Spinnaker observability, such as removing the service name for each metric so that you can more easily organize and filter metrics for cross-Spinnaker visibility. They also create a more efficient implementation and dramatically reduce CPU and memory usage.
Following is the sequence of activities for enabling the Observability Plugin:
Update Spinnaker Images
Configuration to Enable Observability Plugin
Update the Spinnaker Images
To enable the Observability Plugin metrics we need to update all the spinnaker images with permissions enabled for the Plugin Directory as instructed below:
Navigate to default/profiles/service-settings
Update all the below images as per the service:
Configuration Update to Enable Observability Plugin
Below configuration instructions need to be followed to Enable Observability Plugin.
Clone the repo by using the below command.
After cloning the above repo, Navigate to “ObservabilityPluginConfiguration” directory and copy the configurations from all the files.
Note: Ensure to Compare the yaml with your current existing configurations and do not overwrite any existing change. Just Copy the Plugin Part
Update the configuration for all the spinnaker services in order to capture the metrics for every service individually.
Navigate to default/profiles.
Edit each Individual service-local yaml file and update the below data into it.
Restart the halyard pod, after updating the above changes.
Last updated