Detecting Services from Git Integrations
By default, OpsLevel will automatically recommend services that we detect may be in your repo when you integrate a git repository. These recommendations can be found by clicking the Detected Services button within the Service Show page.
Once in the Detected Services page, you will see a list of Pending Services that OpsLevel has detected from your repositories. From this list, you will be able to see the Service Name, where the Service was detected from, and when the Service was detected.
If you see a Recommended Service or Services that you want to add to your Service Catalog, you can add it by selecting the Service(s) and clicking Accept from either the Actions column or the Bulk Actions dropdown.
If you see a Recommended Service or Services that you do not want added to your Service Catalog, you can ignore them by selecting the Service(s) and clicking Ignore from either the Actions column or the Bulk Actions dropdown.
Any action that you take is recorded to help you audit any events created from suggestions in the Recent Activities tab.
Unignoring Recommended Services
If you've accidentally ignored a Recommended Service, you can add them back to the Pending Services list. Selecting Ignored from the Status dropdown will display all of the Recommended Services that have been set to Ignore. You can add these Services back to the Pending Services list selecting the Service(s) and clicking Unignore from either the Actions column or the Bulk Actions dropdown.
Disabling Detected Services
While Service Detection is enabled by default it can be disabled from the integration page for your git repository. In the Integration page for your git repo, there is a Disable Service Detection button within the Service Detection card. Clicking this button will pause service recommendations for that integration as well as remove existing recommendations from the Service Detection page. If at a later time you want to resume receiving Service Recommendations, you can do so by clicking the Enable Service Detection button. Re-enabling Service Detection will also bring back any recommendations that were removed when disabling.
Detecting Service Aliases from Deploy and Check Events
If OpsLevel is sent a deploy or a check with a service identifier that we don’t recognize yet, we will suggest that you either add a new service or add it as an alias to an existing service.
You’ll find the suggestions on the Detected Services page, under the Aliases tab. We show a list of unique service identifiers that we’ve received from deploys or checks, but didn’t match directly to any known service. We also display the source of each service identifier in the Source column. We will suggest mapping the deploy or check result to an existing service if the name is similar, otherwise we will suggest adding a new service to OpsLevel.
Review the suggestions and make any changes to the action or service name. The actions are:
- Create - Make a new service and attach the associated deploys and check results.
- Map - Attach the alias to the existing service and merge the new deploys/check results with the old deploys/check results.
Once the action and service name are correct, hit Accept to take the suggested action.
You can also hide the suggestions if they aren’t helpful by clicking Ignore. You can view ignored suggestions by changing the filter from Status: Pending to Status: Ignored. You can then have them show again by clicking Unignore.
Note: Ignoring suggestions will ignore them for the entire account.