Schema Registry Management and Operations Auditable Event Methods on Confluent Cloud

An auditable event is an action on a Schema Registry, Stream Catalog, schema exporter, or Data Encryption Key (DEK) Registry resource that Confluent Cloud logs for security and compliance review. An auditable event triggers its auditable event method, which sends a message that Confluent Cloud stores as an audit log record.

The following actions, or operations, on Schema Registry, Stream Catalog, schema exporters, and DEK Registry generate auditable event messages for the io.confluent.sg.server/request event type. For authentication and authorization events for Schema Registry, see Schema Registry Authentication and Authorization Auditable Event Methods on Confluent Cloud.

For information about the Schema Registry and Stream Catalog REST APIs used to perform these operations, see the Schema Registry API (V1), Confluent Cloud Schema Registry REST API Usage Examples, and Stream Catalog REST API usage guide.

Schema Registry examples
Stream Catalog examples
Schema exporter examples
Data encryption key registry examples

All method names are prefixed with schema-registry, regardless of whether they represent operations on Schema Registry, Stream Catalog, schema exporters, or DEK Registry. For example, the methodName for the RegisterSchema method is schema-registry.RegisterSchema.

All of these requests are of type io.confluent.sg.server/request.

Schema Registry management auditable event methods have the same method names as the Schema Registry authorization event methods.

Schema Registry examples

Method name	Action triggering an auditable event message
schema-registry.RegisterSchema	Register a new schema under the specified subject.
schema-registry.DeleteSchemaVersion	Delete a specific version of the schema registered under this subject.
schema-registry.DeleteSubject	Delete the specified subject and its associated compatibility level if registered.
schema-registry.UpdateSubjectConfig	Update the subject compatibility level.
schema-registry.DeleteSubjectConfig	Delete the specified subject-level compatibility level configuration and revert to the global default.
schema-registry.UpdateGlobalConfig	Update the global compatibility level.
schema-registry.DeleteGlobalConfig	Delete the global compatibility level configuration and revert to the default.
schema-registry.UpdateSubjectMode	Update the mode for the specified subject.
schema-registry.DeleteSubjectMode	Delete the mode for the specified subject.
schema-registry.UpdateGlobalMode	Update the global mode.
schema-registry.CreateAssociation	Create an association between a resource and a schema subject.
schema-registry.CreateOrUpdateAssociation	Create or update the association for a specific resource.
schema-registry.MutateAssociations	Batch create, update, or delete associations across one or more resources.
schema-registry.BatchGetAssociations	Retrieve associations for one or more resources.
schema-registry.DeleteAssociations	Delete all associations for a resource.

schema-registry.RegisterSchema

The schema-registry.RegisterSchema event is generated by a request to register a new schema under the specified subject using POST /subjects/(string: subject)/versions.

A successful request returns "result": {"status": "SUCCESS"}; a failed request returns "result": {"status": "FAILURE"} with an errorCode and errorMessage.

To view example event messages, expand the following dropdowns:

schema-registry.DeleteSchemaVersion

The schema-registry.DeleteSchemaVersion event is generated by a request to delete a specific version of the schema registered under this subject using DELETE /subjects/(string: subject)/versions/(versionId: version).

A successful request returns "result": {"status": "SUCCESS"}; a failed request returns "result": {"status": "FAILURE"} with an errorCode and errorMessage.

To view example event messages, expand the following dropdowns:

schema-registry.DeleteSubject

The schema-registry.DeleteSubject event is generated by a request to delete the specified subject and its associated compatibility level if registered using DELETE /subjects/(string: subject).

A successful request returns "result": {"status": "SUCCESS"}; a failed request returns "result": {"status": "FAILURE"} with an errorCode and errorMessage.

To view example event messages, expand the following dropdowns:

schema-registry.UpdateSubjectConfig

The schema-registry.UpdateSubjectConfig event is generated by a request to update the subject compatibility level using PUT /config/(string: subject).

A successful request returns "result": {"status": "SUCCESS"}; a failed request returns "result": {"status": "FAILURE"} with an errorCode and errorMessage.

To view example event messages, expand the following dropdowns:

schema-registry.DeleteSubjectConfig

The schema-registry.DeleteSubjectConfig event is generated by a request to delete the specified subject-level compatibility level configuration and revert to the global default using DELETE /config/(string: subject).

A successful request returns "result": {"status": "SUCCESS"}; a failed request returns "result": {"status": "FAILURE"} with an errorCode and errorMessage.

To view example event messages, expand the following dropdowns:

schema-registry.UpdateGlobalConfig

The schema-registry.UpdateGlobalConfig event is generated by a request to update the global compatibility level using PUT /config.

A successful request returns "result": {"status": "SUCCESS"}; a failed request returns "result": {"status": "FAILURE"} with an errorCode and errorMessage.

To view example event messages, expand the following dropdowns:

schema-registry.DeleteGlobalConfig

The schema-registry.DeleteGlobalConfig event is generated by a request to delete the global compatibility level configuration and revert to the default using DELETE /config.

A successful request returns "result": {"status": "SUCCESS"}; a failed request returns "result": {"status": "FAILURE"} with an errorCode and errorMessage.

To view example event messages, expand the following dropdowns:

schema-registry.UpdateSubjectMode

The schema-registry.UpdateSubjectMode event is generated by a request to update the mode for the specified subject using PUT /mode/(string: subject).

A successful request returns "result": {"status": "SUCCESS"}; a failed request returns "result": {"status": "FAILURE"} with an errorCode and errorMessage.

To view example event messages, expand the following dropdowns:

schema-registry.DeleteSubjectMode

The schema-registry.DeleteSubjectMode event is generated by a request to delete the mode for the specified subject using DELETE /mode/(string: subject).

A successful request returns "result": {"status": "SUCCESS"}; a failed request returns "result": {"status": "FAILURE"} with an errorCode and errorMessage.

To view example event messages, expand the following dropdowns:

schema-registry.UpdateGlobalMode

The schema-registry.UpdateGlobalMode event is generated by a request to update the global mode using PUT /mode.

A successful request returns "result": {"status": "SUCCESS"}; a failed request returns "result": {"status": "FAILURE"} with an errorCode and errorMessage.

To view example event messages, expand the following dropdowns:

schema-registry.CreateAssociation

The schema-registry.CreateAssociation event is generated by a request to create an association between a resource and a schema subject using POST /associations.

A successful request returns "result": {"status": "SUCCESS"}; a failed request returns "result": {"status": "FAILURE"} with an errorCode and errorMessage.

To view example event messages, expand the following dropdowns:

Success

{
  "datacontenttype": "application/json",
  "data": {
    "serviceName": "crn://confluent.cloud/",
    "methodName": "schema-registry.CreateAssociation",
    "cloudResources": [
      {
        "scope": {
          "resources": [
            { "type": "ORGANIZATION", "resourceId": "abc-123" },
            { "type": "ENVIRONMENT", "resourceId": "env-abc123" }
          ]
        },
        "resource": { "type": "SCHEMA_REGISTRY", "resourceId": "lsrc-abc123" }
      }
    ],
    "authenticationInfo": {
      "exposure": "CUSTOMER",
      "principal": { "confluentUser": { "resourceId": "u-abc123" } },
      "result": "SUCCESS",
      "credentials": {
        "idSecretCredentials": { "credentialId": "APIKEY1" },
        "mechanism": "HTTP_BASIC"
      }
    },
    "authorizationInfo": { "result": "ALLOW" },
    "requestMetadata": {
      "requestId": ["ab12cd34-ef56-7890-ab12-cd34ef567890"],
      "clientAddress": [{ "ip": "203.0.113.5" }]
    },
    "request": {
      "accessType": "MODIFICATION",
      "data": {
        "resourceName": "crn://confluent.cloud/organization=abc-123/environment=env-abc123/cloud-cluster=lkc-abc123",
        "resourceNamespace": "KAFKA_CLUSTER",
        "resourceId": "lkc-abc123",
        "resourceType": "topic",
        "associations": [
          {
            "subject": "orders-value",
            "associationType": "value",
            "lifecycle": "STRONG",
            "frozen": false,
            "normalize": true,
            "schema": "[redacted]"
          }
        ]
      }
    },
    "result": {
      "status": "SUCCESS",
      "data": {
        "resourceName": "crn://confluent.cloud/organization=abc-123/environment=env-abc123/cloud-cluster=lkc-abc123",
        "resourceNamespace": "KAFKA_CLUSTER",
        "resourceId": "lkc-abc123",
        "resourceType": "topic",
        "associations": [
          {
            "subject": "orders-value",
            "associationType": "value",
            "lifecycle": "STRONG",
            "frozen": false,
            "schema": "[redacted]"
          }
        ]
      }
    },
    "resourceName": "crn://confluent.cloud/organization=abc-123/environment=env-abc123/schema-registry=lsrc-abc123"
  },
  "subject": "crn://confluent.cloud/organization=abc-123/environment=env-abc123/schema-registry=lsrc-abc123",
  "specversion": "1.0",
  "id": "ab12cd34-ef56-7890-ab12-cd34ef567890",
  "source": "crn://confluent.cloud/",
  "time": "2026-08-06T12:00:00.000Z",
  "type": "io.confluent.sg.server/request"
}

schema-registry.CreateOrUpdateAssociation

The schema-registry.CreateOrUpdateAssociation event is generated by a request to create or update the association for a specific resource using PUT /associations/resources/(string: resource).

A successful request returns "result": {"status": "SUCCESS"}; a failed request returns "result": {"status": "FAILURE"} with an errorCode and errorMessage.

To view example event messages, expand the following dropdowns:

Success

{
  "datacontenttype": "application/json",
  "data": {
    "serviceName": "crn://confluent.cloud/",
    "methodName": "schema-registry.CreateOrUpdateAssociation",
    "cloudResources": [
      {
        "scope": {
          "resources": [
            { "type": "ORGANIZATION", "resourceId": "abc-123" },
            { "type": "ENVIRONMENT", "resourceId": "env-abc123" }
          ]
        },
        "resource": { "type": "SCHEMA_REGISTRY", "resourceId": "lsrc-abc123" }
      }
    ],
    "authenticationInfo": {
      "exposure": "CUSTOMER",
      "principal": { "confluentUser": { "resourceId": "u-abc123" } },
      "result": "SUCCESS",
      "credentials": {
        "idSecretCredentials": { "credentialId": "APIKEY1" },
        "mechanism": "HTTP_BASIC"
      }
    },
    "authorizationInfo": { "result": "ALLOW" },
    "requestMetadata": {
      "requestId": ["ab12cd34-ef56-7890-ab12-cd34ef567890"],
      "clientAddress": [{ "ip": "203.0.113.5" }]
    },
    "request": {
      "accessType": "MODIFICATION",
      "data": {
        "resourceName": "crn://confluent.cloud/organization=abc-123/environment=env-abc123/cloud-cluster=lkc-abc123",
        "resourceNamespace": "KAFKA_CLUSTER",
        "resourceId": "lkc-abc123",
        "resourceType": "topic",
        "associations": [
          {
            "subject": "orders-key",
            "associationType": "key",
            "lifecycle": "STRONG",
            "frozen": true,
            "normalize": false,
            "schema": "[redacted]"
          }
        ]
      }
    },
    "result": {
      "status": "SUCCESS",
      "data": {
        "resourceName": "crn://confluent.cloud/organization=abc-123/environment=env-abc123/cloud-cluster=lkc-abc123",
        "resourceNamespace": "KAFKA_CLUSTER",
        "resourceId": "lkc-abc123",
        "resourceType": "topic",
        "associations": [
          {
            "subject": "orders-key",
            "associationType": "key",
            "lifecycle": "STRONG",
            "frozen": true,
            "schema": "[redacted]"
          }
        ]
      }
    },
    "resourceName": "crn://confluent.cloud/organization=abc-123/environment=env-abc123/schema-registry=lsrc-abc123"
  },
  "subject": "crn://confluent.cloud/organization=abc-123/environment=env-abc123/schema-registry=lsrc-abc123",
  "specversion": "1.0",
  "id": "ab12cd34-ef56-7890-ab12-cd34ef567890",
  "source": "crn://confluent.cloud/",
  "time": "2026-08-06T12:00:00.000Z",
  "type": "io.confluent.sg.server/request"
}

schema-registry.MutateAssociations

The schema-registry.MutateAssociations event is generated by a request to batch create, update, or delete associations across one or more resources using POST /associations:batchMutate.

A successful request returns "result": {"status": "SUCCESS"}; a failed request returns "result": {"status": "FAILURE"} with an errorCode and errorMessage.

To view example event messages, expand the following dropdowns:

Success

{
  "datacontenttype": "application/json",
  "data": {
    "serviceName": "crn://confluent.cloud/",
    "methodName": "schema-registry.MutateAssociations",
    "cloudResources": [
      {
        "scope": {
          "resources": [
            { "type": "ORGANIZATION", "resourceId": "abc-123" },
            { "type": "ENVIRONMENT", "resourceId": "env-abc123" }
          ]
        },
        "resource": { "type": "SCHEMA_REGISTRY", "resourceId": "lsrc-abc123" }
      }
    ],
    "authenticationInfo": {
      "exposure": "CUSTOMER",
      "principal": { "confluentUser": { "resourceId": "u-abc123" } },
      "result": "SUCCESS",
      "credentials": {
        "idSecretCredentials": { "credentialId": "APIKEY1" },
        "mechanism": "HTTP_BASIC"
      }
    },
    "authorizationInfo": { "result": "ALLOW" },
    "requestMetadata": {
      "requestId": ["ab12cd34-ef56-7890-ab12-cd34ef567890"],
      "clientAddress": [{ "ip": "203.0.113.5" }]
    },
    "request": {
      "accessType": "MODIFICATION",
      "data": {
        "requests": [
          {
            "resourceName": "crn://confluent.cloud/organization=abc-123/environment=env-abc123/cloud-cluster=lkc-abc123",
            "resourceNamespace": "KAFKA_CLUSTER",
            "resourceId": "lkc-abc123",
            "resourceType": "topic",
            "associations": [
              {
                "opType": "UPSERT",
                "subject": "orders-value",
                "associationType": "value",
                "lifecycle": "STRONG",
                "frozen": false,
                "normalize": true,
                "schema": "[redacted]"
              },
              {
                "opType": "DELETE",
                "subject": "orders-key",
                "associationType": "key"
              }
            ]
          }
        ]
      }
    },
    "result": {
      "status": "SUCCESS",
      "data": {
        "results": [
          {
            "result": {
              "resourceName": "crn://confluent.cloud/organization=abc-123/environment=env-abc123/cloud-cluster=lkc-abc123",
              "resourceNamespace": "KAFKA_CLUSTER",
              "resourceId": "lkc-abc123",
              "resourceType": "topic",
              "associations": [
                {
                  "subject": "orders-value",
                  "associationType": "value",
                  "lifecycle": "STRONG",
                  "frozen": false,
                  "schema": "[redacted]"
                }
              ]
            }
          }
        ]
      }
    },
    "resourceName": "crn://confluent.cloud/organization=abc-123/environment=env-abc123/schema-registry=lsrc-abc123"
  },
  "subject": "crn://confluent.cloud/organization=abc-123/environment=env-abc123/schema-registry=lsrc-abc123",
  "specversion": "1.0",
  "id": "ab12cd34-ef56-7890-ab12-cd34ef567890",
  "source": "crn://confluent.cloud/",
  "time": "2026-08-06T12:00:00.000Z",
  "type": "io.confluent.sg.server/request"
}

schema-registry.BatchGetAssociations

The schema-registry.BatchGetAssociations event is generated by a request to retrieve associations for one or more resources using POST /associations:batchGet.

A successful request returns "result": {"status": "SUCCESS"}; a failed request returns "result": {"status": "FAILURE"} with an errorCode and errorMessage.

To view example event messages, expand the following dropdowns:

Success

{
  "datacontenttype": "application/json",
  "data": {
    "serviceName": "crn://confluent.cloud/",
    "methodName": "schema-registry.BatchGetAssociations",
    "cloudResources": [
      {
        "scope": {
          "resources": [
            { "type": "ORGANIZATION", "resourceId": "abc-123" },
            { "type": "ENVIRONMENT", "resourceId": "env-abc123" }
          ]
        },
        "resource": { "type": "SCHEMA_REGISTRY", "resourceId": "lsrc-abc123" }
      }
    ],
    "authenticationInfo": {
      "exposure": "CUSTOMER",
      "principal": { "confluentUser": { "resourceId": "u-abc123" } },
      "result": "SUCCESS",
      "credentials": {
        "idSecretCredentials": { "credentialId": "APIKEY1" },
        "mechanism": "HTTP_BASIC"
      }
    },
    "authorizationInfo": { "result": "ALLOW" },
    "requestMetadata": {
      "requestId": ["ab12cd34-ef56-7890-ab12-cd34ef567890"],
      "clientAddress": [{ "ip": "203.0.113.5" }]
    },
    "request": {
      "accessType": "READ_ONLY",
      "data": {
        "requests": [
          {
            "resourceName": "crn://confluent.cloud/organization=abc-123/environment=env-abc123/cloud-cluster=lkc-abc123",
            "resourceNamespace": "KAFKA_CLUSTER",
            "resourceId": "lkc-abc123",
            "resourceType": "topic",
            "associationTypes": ["key", "value"],
            "lifecycle": "STRONG"
          }
        ]
      }
    },
    "result": {
      "status": "SUCCESS",
      "data": {
        "results": [
          {
            "result": {
              "resourceName": "crn://confluent.cloud/organization=abc-123/environment=env-abc123/cloud-cluster=lkc-abc123",
              "resourceNamespace": "KAFKA_CLUSTER",
              "resourceId": "lkc-abc123",
              "resourceType": "topic",
              "associations": [
                {
                  "subject": "orders-value",
                  "associationType": "value",
                  "lifecycle": "STRONG",
                  "frozen": false,
                  "schema": "[redacted]"
                }
              ]
            }
          }
        ]
      }
    },
    "resourceName": "crn://confluent.cloud/organization=abc-123/environment=env-abc123/schema-registry=lsrc-abc123"
  },
  "subject": "crn://confluent.cloud/organization=abc-123/environment=env-abc123/schema-registry=lsrc-abc123",
  "specversion": "1.0",
  "id": "ab12cd34-ef56-7890-ab12-cd34ef567890",
  "source": "crn://confluent.cloud/",
  "time": "2026-08-06T12:00:00.000Z",
  "type": "io.confluent.sg.server/request"
}

schema-registry.DeleteAssociations

The schema-registry.DeleteAssociations event is generated by a request to delete all associations for a resource using DELETE /associations/resources/(string: resource).

A successful request returns "result": {"status": "SUCCESS"}; a failed request returns "result": {"status": "FAILURE"} with an errorCode and errorMessage.

To view example event messages, expand the following dropdowns:

Stream Catalog examples

Method name	Action triggering an auditable event message
schema-registry.PartialEntityUpdate	Partially update an entity.
schema-registry.CreateTags	Create tags.
schema-registry.UpdateTags	Update tags.
schema-registry.DeleteTag	Delete a tag on an entity.
schema-registry.CreateBusinessMetadata	Create business metadata.
schema-registry.UpdateBusinessMetadata	Update business metadata.
schema-registry.DeleteBusinessMetadata	Delete business metadata on an entity.
schema-registry.CreateTagDefs	Create tag definitions.
schema-registry.UpdateTagDefs	Update tag definitions.
schema-registry.DeleteTagDef	Delete tag definitions identified by their names.
schema-registry.CreateBusinessMetadataDefs	Create business metadata definitions.
schema-registry.UpdateBusinessMetadataDefs	Update business metadata definitions.
schema-registry.DeleteBusinessMetadataDef	Delete a business metadata definition identified by its name.
schema-registry.UpdateSchemaTags	Bulk-update multiple tags.

schema-registry.PartialEntityUpdate

The schema-registry.PartialEntityUpdate event is generated by a request to partially update an entity.

A successful request returns "result": {"status": "SUCCESS"}; a failed request returns "result": {"status": "FAILURE"} with an errorCode and errorMessage.

To view example event messages, expand the following dropdowns:

schema-registry.CreateTags

The schema-registry.CreateTags event is generated by a request to create tags using POST catalog/v1/entity/tags.

A successful request returns "result": {"status": "SUCCESS"}; a failed request returns "result": {"status": "FAILURE"} with an errorCode and errorMessage.

To view example event messages, expand the following dropdowns:

schema-registry.UpdateTags

The schema-registry.UpdateTags event is generated by a request to update tags using PUT catalog/v1/entity/tags.

A successful request returns "result": {"status": "SUCCESS"}; a failed request returns "result": {"status": "FAILURE"} with an errorCode and errorMessage.

To view example event messages, expand the following dropdowns:

schema-registry.DeleteTag

The schema-registry.DeleteTag event is generated by a request to delete a tag on an entity using DELETE catalog/v1/entity/type/(string: typeName)/name/(string: qualifiedName)/tags/(string: tagName).

A successful request returns "result": {"status": "SUCCESS"}; a failed request returns "result": {"status": "FAILURE"} with an errorCode and errorMessage.

To view example event messages, expand the following dropdowns:

schema-registry.CreateBusinessMetadata

The schema-registry.CreateBusinessMetadata event is generated by a request to create business metadata using POST catalog/v1/entity/businessmetadata.

A successful request returns "result": {"status": "SUCCESS"}; a failed request returns "result": {"status": "FAILURE"} with an errorCode and errorMessage.

To view example event messages, expand the following dropdowns:

schema-registry.UpdateBusinessMetadata

The schema-registry.UpdateBusinessMetadata event is generated by a request to update business metadata using PUT catalog/v1/entity/businessmetadata.

A successful request returns "result": {"status": "SUCCESS"}; a failed request returns "result": {"status": "FAILURE"} with an errorCode and errorMessage.

To view example event messages, expand the following dropdowns:

schema-registry.DeleteBusinessMetadata

The schema-registry.DeleteBusinessMetadata event is generated by a request to delete business metadata on an entity using DELETE catalog/v1/entity/type/(string: typeName)/name/(string: qualifiedName)/businessmetadata/(string: bmName).

A successful request returns "result": {"status": "SUCCESS"}; a failed request returns "result": {"status": "FAILURE"} with an errorCode and errorMessage.

To view example event messages, expand the following dropdowns:

schema-registry.CreateTagDefs

The schema-registry.CreateTagDefs event is generated by a request to create tag definitions using POST catalog/v1/types/tagdefs.

A successful request returns "result": {"status": "SUCCESS"}; a failed request returns "result": {"status": "FAILURE"} with an errorCode and errorMessage.

To view example event messages, expand the following dropdowns:

schema-registry.UpdateTagDefs

The schema-registry.UpdateTagDefs event is generated by a request to update tag definitions using PUT catalog/v1/types/tagdefs.

A successful request returns "result": {"status": "SUCCESS"}; a failed request returns "result": {"status": "FAILURE"} with an errorCode and errorMessage.

To view example event messages, expand the following dropdowns:

schema-registry.DeleteTagDef

The schema-registry.DeleteTagDef event is generated by a request to delete tag definitions identified by their names using DELETE catalog/v1/types/tagdefs/(string: tagName).

A successful request returns "result": {"status": "SUCCESS"}; a failed request returns "result": {"status": "FAILURE"} with an errorCode and errorMessage.

To view example event messages, expand the following dropdowns:

schema-registry.CreateBusinessMetadataDefs

The schema-registry.CreateBusinessMetadataDefs event is generated by a request to create business metadata definitions using POST catalog/v1/types/businessmetadatadefs.

A successful request returns "result": {"status": "SUCCESS"}; a failed request returns "result": {"status": "FAILURE"} with an errorCode and errorMessage.

To view example event messages, expand the following dropdowns:

schema-registry.UpdateBusinessMetadataDefs

The schema-registry.UpdateBusinessMetadataDefs event is generated by a request to update business metadata definitions using PUT catalog/v1/types/businessmetadatadefs.

A successful request returns "result": {"status": "SUCCESS"}; a failed request returns "result": {"status": "FAILURE"} with an errorCode and errorMessage.

To view example event messages, expand the following dropdowns:

schema-registry.DeleteBusinessMetadataDef

The schema-registry.DeleteBusinessMetadataDef event is generated by a request to delete a business metadata definition identified by its name using DELETE catalog/v1/types/businessmetadatadefs/(string: bmName).

A successful request returns "result": {"status": "SUCCESS"}; a failed request returns "result": {"status": "FAILURE"} with an errorCode and errorMessage.

To view example event messages, expand the following dropdowns:

schema-registry.UpdateSchemaTags

The schema-registry.UpdateSchemaTags event is generated by a request to bulk-update multiple tags using PUT catalog/v1/entity/tags.

A successful request returns "result": {"status": "SUCCESS"}; a failed request returns "result": {"status": "FAILURE"} with an errorCode and errorMessage.

To view example event messages, expand the following dropdowns:

Schema exporter examples

Method name	Action triggering an auditable event message
schema-registry.CreateExporter	Create a schema exporter.
schema-registry.UpdateExporter	Update schema exporter by name.
schema-registry.UpdateExporterConfig	Update schema exporter configuration by name.
schema-registry.PauseExporter	Pause schema exporter by name.
schema-registry.ResetExporter	Reset schema exporter by name.
schema-registry.ResumeExporter	Resume schema exporter by name.
schema-registry.DeleteExporter	Delete schema exporter by name.

schema-registry.CreateExporter

The schema-registry.CreateExporter event is generated by a request to create a schema exporter using POST /exporters.

A successful request returns "result": {"status": "SUCCESS"}; a failed request returns "result": {"status": "FAILURE"} with an errorCode and errorMessage.

To view example event messages, expand the following dropdowns:

schema-registry.UpdateExporter

The schema-registry.UpdateExporter event is generated by a request to update a schema exporter by name using PUT /exporters/(string: name).

A successful request returns "result": {"status": "SUCCESS"}; a failed request returns "result": {"status": "FAILURE"} with an errorCode and errorMessage.

To view example event messages, expand the following dropdowns:

schema-registry.UpdateExporterConfig

The schema-registry.UpdateExporterConfig event is generated by a request to update schema exporter configuration by name using PUT /exporters/(string: name)/config.

A successful request returns "result": {"status": "SUCCESS"}; a failed request returns "result": {"status": "FAILURE"} with an errorCode and errorMessage.

To view example event messages, expand the following dropdowns:

schema-registry.PauseExporter

The schema-registry.PauseExporter event is generated by a request to pause a schema exporter by name using PUT /exporters/(string: name)/pause.

A successful request returns "result": {"status": "SUCCESS"}; a failed request returns "result": {"status": "FAILURE"} with an errorCode and errorMessage.

To view example event messages, expand the following dropdowns:

schema-registry.ResetExporter

The schema-registry.ResetExporter event is generated by a request to reset schema exporter by name using PUT /exporters/(string: name)/reset.

A successful request returns "result": {"status": "SUCCESS"}; a failed request returns "result": {"status": "FAILURE"} with an errorCode and errorMessage.

To view example event messages, expand the following dropdowns:

schema-registry.ResumeExporter

The schema-registry.ResumeExporter event is generated by a request to resume schema exporter by name using PUT /exporters/(string: name)/resume.

A successful request returns "result": {"status": "SUCCESS"}; a failed request returns "result": {"status": "FAILURE"} with an errorCode and errorMessage.

To view example event messages, expand the following dropdowns:

schema-registry.DeleteExporter

The schema-registry.DeleteExporter event is generated by a request to delete schema exporter by name using DELETE /exporters/(string: name).

A successful request returns "result": {"status": "SUCCESS"}; a failed request returns "result": {"status": "FAILURE"} with an errorCode and errorMessage.

To view example event messages, expand the following dropdowns:

Data encryption key registry examples

The following methods relate to actions on data encryption key (DEK) and key encryption key (KEK). The KEK is used to encrypt the DEK. The DEK is used to encrypt the data itself. The KEK is under the customer’s control and points to a keystore such as the customer’s Azure Key Vault, AWS Key Management Service (KMS), or Google Cloud KMS.

Method name	Action triggering an auditable event message
schema-registry.RegisterKek	Register a key encryption key.
schema-registry.UpdateKek	Update a key encryption key.
schema-registry.DeregisterKek	Deregister a key encryption key.
schema-registry.RegisterDek	Register a data encryption key.
schema-registry.GetDek	Retrieve a data encryption key.
schema-registry.DeregisterDek	Deregister a data encryption key.

schema-registry.RegisterKek

The schema-registry.RegisterKek event is generated by a request to register a key encryption key.

A successful request returns "result": {"status": "SUCCESS"}; a failed request returns "result": {"status": "FAILURE"} with an errorCode and errorMessage.

To view example event messages, expand the following dropdowns:

schema-registry.UpdateKek

The schema-registry.UpdateKek event is generated by a request to update a key encryption key.

A successful request returns "result": {"status": "SUCCESS"}; a failed request returns "result": {"status": "FAILURE"} with an errorCode and errorMessage.

To view example event messages, expand the following dropdowns:

schema-registry.DeregisterKek

The schema-registry.DeregisterKek event is generated by a request to deregister a key encryption key.

A successful request returns "result": {"status": "SUCCESS"}; a failed request returns "result": {"status": "FAILURE"} with an errorCode and errorMessage.

To view example event messages, expand the following dropdowns:

schema-registry.RegisterDek

The schema-registry.RegisterDek event is generated by a request to register a data encryption key.

A successful request returns "result": {"status": "SUCCESS"}; a failed request returns "result": {"status": "FAILURE"} with an errorCode and errorMessage.

To view example event messages, expand the following dropdowns:

schema-registry.GetDek

The schema-registry.GetDek event is generated by a request to retrieve a data encryption key.

A successful request returns "result": {"status": "SUCCESS"}; a failed request returns "result": {"status": "FAILURE"} with an errorCode and errorMessage.

To view example event messages, expand the following dropdowns:

schema-registry.DeregisterDek

The schema-registry.DeregisterDek event is generated by a request to deregister a data encryption key.

A successful request returns "result": {"status": "SUCCESS"}; a failed request returns "result": {"status": "FAILURE"} with an errorCode and errorMessage.

To view example event messages, expand the following dropdowns: