Linking and de-linking technical services

understand how to manage technical service links that associate one technical service with another in accordance with the pipeline requirements to ensure technical compliance linking technical service provides a feature to link technical services auto linked technical services can be linked to another technical service in accordance with pipeline requirements the following are key points to consider regarding the linking technical service feature technical services are auto linked for a few endpoints but mapping your technical service is always a good idea for example, if, in the configure technical service table, you see multiple entries for a single service linked to different endpoints, you can map them together to a single service as your pipeline scenarios where auto linking of technical service is possible if the same tools provide data to two pages, say jenkins provides test and build data if repository name can be retrieved from the data say travis ci and git service sharing the same reponame gets auto linked suppose a repo in git is named demo121 and in travis (build) is demo121 but in sonarqube (test) the name of the project linked to the build tool is releasedemo in that case, the releasedemo of sonarqube(test) can be mapped/ linked to the above service (demo121) resulting in creating a single service for your pipeline note this stage is important as it has a direct impact on metering to link technical services, perform the following steps go to settings & utilities → configure technical service the technical service tab shows a list of filters that can be used to filter and see data in the table below the filters the following is the list of filters available to select from application develop tool build tool test tool deploy tool run tool static scan container vulnerability scan dependency check after selecting any required filters, a list of technical services will appear, where technical services can be clicked on for example, the nginx technical service discovered from google and choose the nginx technical service discovered by xunit (discovered using byot ) and click on update when the previous step has been completed, you see that nginx technical service is discovered by different tools and is now mapped to a single technical service, and a pipeline is created with the test stage in kyndryl modern operations applications – , this technical service will be visible in the test dashboard of at this point, if a search is performed for nginx technical service, you see that both run and test technical services have been linked together as per the pipeline requirements important linking technical services of the same type is not possible, for example, a technical service registered by sonarqube and byot is not possible as both will have the same service type i e test if a technical service registered by jira and git are linked, two separate rows will be shown in the develop dashboard technical service view with the same name but will show individual tools data after linking technical services manually, technical services which were selected for linking on the link technical service tab will no longer be visible on the main technical service page as they will be mapped to a technical service, but this technical service can still be seen on the linked technical service tab de linking technical service provides a feature to de link a previously linked service auto linked technical services can be de linked and linked to other technical services per the pipeline requirements to de link technical service, perform the following steps go to settings & utilities → configure technical service select any technical service that was previously linked (for example, nginx) select linked technical service tab select the technical service to be delinked select delink technical service , continue with the confirmation on confirmation, the request for de linking will be accepted and the technical service will start existing as an independent technical service note the request will be accepted for de linking, the individual technical service might take one sync interval (up to 5 minutes) to show up on the respective dashboards