Skip to main content

REST APIs for 24.2.20 and 24.2.10

Core Services Detection

This Public Experimental API helps you identify core services and suggests an appropriate label. 51 services can be detected.

Core services (such as DNS, Domain Controller, NTP, and LDP) are essential to your computing environment and run on one or multiple workloads. Identifying and labeling these workloads is important because they are centrally connected, and other applications depend on them.

When you use core service detection to label and write policies for core services, you can save time on application policies and introduce enforcement faster.

Users can change port numbers on which a specific core service is running so that they can adjust them to their environment. Users cannot change ports using the UI, only the APIs.

The user authorized to manage core services is the Organization Administrator.

The Common schemas for managing core services:

  • core_services_labels.schema.json

  • core_services_type_ports_def.schema.json

  • core_services_type_ports.schema.json

Core Services API Methods

Functionality

HTTP

URI

Get all detected core services for this organization.

GET

[api_version][org_href]/detected_core_services

Get a detected core service by UUID.

GET

[api_version][org_href]/detected_core_services/<uuid>

Get detected core service summary details.

GET

[api_version][org_href]/detected_core_services_summary

Get all core service types for this organization.

GET

[api_version][org_href]/core_service_types

Get core service type by UUID.

GET

[api_version][org_href]/core_service_types/<uuid>

Accept, reject, or skip the core service recommendation.

PUT

[api_version][org_href]/detected_core_services/:uuid

Edit suggested labels of a core service type for the organization.

PUT

[api_version][org_href]/core_service_types/:uuid