Plugins

Get a Zipkin plugin

get/v2/control-planes/{controlPlaneId}/core-entities/plugins/{PluginId}#Zipkin

Response

Zipkin plugin

conditionstring nullable

An expression used for conditional control over plugin execution. If the expression evaluates to true during the request flow, the plugin is executed; otherwise, it is skipped.

created_atinteger nullable

Unix epoch when the resource was created.

enabledboolean nullable

Whether the plugin is applied.

idstring nullable

A string representing a UUID (universally unique identifier).

instance_namestring nullable

A unique string representing a UTF-8 encoded name.

name'zipkin' required

The name of the Plugin that's going to be added. Currently, the Plugin must be installed in every Kong instance separately.

tagsstring[] nullable

An optional set of strings associated with the Plugin for grouping and filtering.

updated_atinteger nullable

Unix epoch when the resource was last updated.

protocolsstring[]

A set of strings representing protocols.

Changes

Changed in 14 of the 52 revisions of this API.22552

Jun 11, 202662c54f1094bb1See the full diff
- ○
  the response property ////// became required for the status
  response-property-became-required
Apr 24, 20267d6a643707d91See the full diff
- ○
  added the optional property //// to the response with the status
  response-optional-property-added
Oct 29, 202519e869275e2812See the full diff
- ▲
  the //// response's property type changed from string to no type for status
  response-property-type-changed
- ○
  the response's property default value 0.01 was removed for the status
  response-property-default-value-removed
- ○
  the response's property default value 0.001 was removed for the status
  response-property-default-value-removed
This revision also has 4 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
Aug 22, 202596118a9cd7f41223See the full diff
- ▲
  the response property ////// became nullable for the status
  response-property-became-nullable
- ▲
  the response property ////// became nullable for the status
  response-property-became-nullable
- ▲
  the response property //// became nullable for the status
  response-property-became-nullable
- ▲
  the response property ///// became nullable for the status
  response-property-became-nullable
- ▲
  the response property ///// became nullable for the status
  response-property-became-nullable
- ▲
  the response property ///// became nullable for the status
  response-property-became-nullable
- ▲
  the response property ////// became nullable for the status
  response-property-became-nullable
- ▲
  the response property ////// became nullable for the status
  response-property-became-nullable
- ▲
  the response property ////// became nullable for the status
  response-property-became-nullable
- ▲
  the response property ///// became nullable for the status
  response-property-became-nullable
- ▲
  the response property ////// became nullable for the status
  response-property-became-nullable
- ▲
  the response property ///// became nullable for the status
  response-property-became-nullable
- ○
  the response's property default value 1 was added for the status
  response-property-default-value-added
- ○
  the response's property default value 2000 was added for the status
  response-property-default-value-added
- ○
  the response's property default value b3 was added for the status
  response-property-default-value-added
- ○
  the response's property default value b3 was added for the status
  response-property-default-value-added
- ○
  the response's property default value true was added for the status
  response-property-default-value-added
- ○
  the response's property default value preserve was added for the status
  response-property-default-value-added
- ○
  the response's property default value method was added for the status
  response-property-default-value-added
- ○
  the response's property default value true was added for the status
  response-property-default-value-added
- ○
  the response's property default value 0.01 was added for the status
  response-property-default-value-added
- ○
  the response's property default value kong was added for the status
  response-property-default-value-added
- ○
  the response's property default value 1 was added for the status
  response-property-default-value-added
- ○
  the response's property default value 1 was added for the status
  response-property-default-value-added
- ○
  the response's property default value 10000 was added for the status
  response-property-default-value-added
- ○
  the response's property default value 60 was added for the status
  response-property-default-value-added
- ○
  the response's property default value 60 was added for the status
  response-property-default-value-added
- ○
  the response's property default value annotations was added for the status
  response-property-default-value-added
- ○
  the response's property default value {"default_format":"b3"} was added for the status
  response-property-default-value-added
- ○
  the response's property default value grpc grpcs http https was added for the status
  response-property-default-value-added
- ○
  the response's property default value 5000 was added for the status
  response-property-default-value-added
- ○
  the response's property default value 0.001 was added for the status
  response-property-default-value-added
- ○
  the response's property default value 5000 was added for the status
  response-property-default-value-added
- ○
  the response's property default value Zipkin-Tags was added for the status
  response-property-default-value-added
- ○
  the response's property default value 16 was added for the status
  response-property-default-value-added
This revision also has 7 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
Aug 12, 20259ca62eba4eca1See the full diff
- ▲
  the response property ////// became optional for the status
  response-property-became-optional
This revision also has 4 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
Jul 22, 20252c77aeaee5fb1See the full diff
- ▲
  the response property //// became nullable for the status
  response-property-became-nullable
Jun 17, 2025c308b7426a7c1See the full diff
- ▲
  the //// response's property format changed from no format to set for status
  response-property-type-changed
May 21, 202569704304ad5f1See the full diff
- ○
  added the optional property //// to the response with the status
  response-optional-property-added
This revision also has 2 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
May 1, 2025351c07039f3c5See the full diff
- ●
  added the new instana enum value to the ///// response property for the response status
  response-property-enum-value-added
- ●
  added the new instana enum value to the ///// response property for the response status
  response-property-enum-value-added
- ●
  added the new instana enum value to the ////// response property for the response status
  response-property-enum-value-added
- ●
  added the new instana enum value to the /////// response property for the response status
  response-property-enum-value-added
- ●
  added the new instana enum value to the /////// response property for the response status
  response-property-enum-value-added
Apr 15, 2025fc6abbc537f322See the full diff
- ▲
  the response property //// became nullable for the status
  response-property-became-nullable
- ▲
  the response property //// became nullable for the status
  response-property-became-nullable
- ○
  the response optional property //// became not read-only for the status
  response-optional-property-became-not-read-only
- ○
  the response optional property //// became not read-only for the status
  response-optional-property-became-not-read-only
This revision also has 7 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

Full history (14 revisions)