Changes to Add a record to the dataset

POST /v1/observability/datasets/{dataset_id}/records

Every recorded change to this endpoint, newest first. Back to the operation

Changed in 3 of the 5 revisions of this API.13737

  1. fa73befe1c613136
  2. 61436a4964045
  3. 933c4ebdcd72111

What changed

  • fa73befe1c613136See the full diff
    • ●

      added the new EVALUATION_RUN_OUTPUT_RECORD_CONFLICT enum value to the // response property for the response status

      response-property-enum-value-added

    • ●

      added the new EVALUATION_RUN_OUTPUT_RECORD_CONFLICT enum value to the // response property for the response status

      response-property-enum-value-added

    • ●

      added the new EVALUATION_RUN_OUTPUT_RECORD_CONFLICT enum value to the // response property for the response status

      response-property-enum-value-added

    • ●

      added the new EVALUATION_RUN_OUTPUT_RECORD_CONFLICT enum value to the // response property for the response status

      response-property-enum-value-added

    • ●

      added the new EVALUATION_RUN_OUTPUT_RECORD_CONFLICT enum value to the // response property for the response status

      response-property-enum-value-added

    • ●

      added the new PIPELINE_CONFIG_ALREADY_EXISTS enum value to the // response property for the response status

      response-property-enum-value-added

    • ●

      added the new PIPELINE_CONFIG_ALREADY_EXISTS enum value to the // response property for the response status

      response-property-enum-value-added

    • ●

      added the new PIPELINE_CONFIG_ALREADY_EXISTS enum value to the // response property for the response status

      response-property-enum-value-added

    • ●

      added the new PIPELINE_CONFIG_ALREADY_EXISTS enum value to the // response property for the response status

      response-property-enum-value-added

    • ●

      added the new PIPELINE_CONFIG_ALREADY_EXISTS enum value to the // response property for the response status

      response-property-enum-value-added

    • ●

      added the new PIPELINE_CONFIG_NOT_FOUND enum value to the // response property for the response status

      response-property-enum-value-added

    • ●

      added the new PIPELINE_CONFIG_NOT_FOUND enum value to the // response property for the response status

      response-property-enum-value-added

    • ●

      added the new PIPELINE_CONFIG_NOT_FOUND enum value to the // response property for the response status

      response-property-enum-value-added

    • ●

      added the new PIPELINE_CONFIG_NOT_FOUND enum value to the // response property for the response status

      response-property-enum-value-added

    • ●

      added the new PIPELINE_CONFIG_NOT_FOUND enum value to the // response property for the response status

      response-property-enum-value-added

    • ●

      added the new SCORER_ALREADY_EXISTS enum value to the // response property for the response status

      response-property-enum-value-added

    • ●

      added the new SCORER_ALREADY_EXISTS enum value to the // response property for the response status

      response-property-enum-value-added

    • ●

      added the new SCORER_ALREADY_EXISTS enum value to the // response property for the response status

      response-property-enum-value-added

    • ●

      added the new SCORER_ALREADY_EXISTS enum value to the // response property for the response status

      response-property-enum-value-added

    • ●

      added the new SCORER_ALREADY_EXISTS enum value to the // response property for the response status

      response-property-enum-value-added

    • ●

      added the new SCORER_CONFIG_KIND_MISMATCH enum value to the // response property for the response status

      response-property-enum-value-added

    • ●

      added the new SCORER_CONFIG_KIND_MISMATCH enum value to the // response property for the response status

      response-property-enum-value-added

    • ●

      added the new SCORER_CONFIG_KIND_MISMATCH enum value to the // response property for the response status

      response-property-enum-value-added

    • ●

      added the new SCORER_CONFIG_KIND_MISMATCH enum value to the // response property for the response status

      response-property-enum-value-added

    • ●

      added the new SCORER_CONFIG_KIND_MISMATCH enum value to the // response property for the response status

      response-property-enum-value-added

    • ●

      added the new SCORER_NOT_FOUND enum value to the // response property for the response status

      response-property-enum-value-added

    • ●

      added the new SCORER_NOT_FOUND enum value to the // response property for the response status

      response-property-enum-value-added

    • ●

      added the new SCORER_NOT_FOUND enum value to the // response property for the response status

      response-property-enum-value-added

    • ●

      added the new SCORER_NOT_FOUND enum value to the // response property for the response status

      response-property-enum-value-added

    • ●

      added the new SCORER_NOT_FOUND enum value to the // response property for the response status

      response-property-enum-value-added

    • ●

      added the new TELEMETRY_SPAN enum value to the response property for the response status

      response-property-enum-value-added

    • ○

      added the new optional request property

      new-optional-request-property

    • ○

      removed the CAMPAIGN_NOT_FOUND enum value from the // response property for the response status

      response-property-enum-value-removed

    • ○

      removed the CAMPAIGN_NOT_FOUND enum value from the // response property for the response status

      response-property-enum-value-removed

    • ○

      removed the CAMPAIGN_NOT_FOUND enum value from the // response property for the response status

      response-property-enum-value-removed

    • ○

      removed the CAMPAIGN_NOT_FOUND enum value from the // response property for the response status

      response-property-enum-value-removed

    • ○

      removed the CAMPAIGN_NOT_FOUND enum value from the // response property for the response status

      response-property-enum-value-removed

    • ○

      removed the CAMPAIGN_NO_MATCHING_EVENTS enum value from the // response property for the response status

      response-property-enum-value-removed

    • ○

      removed the CAMPAIGN_NO_MATCHING_EVENTS enum value from the // response property for the response status

      response-property-enum-value-removed

    • ○

      removed the CAMPAIGN_NO_MATCHING_EVENTS enum value from the // response property for the response status

      response-property-enum-value-removed

    • ○

      removed the CAMPAIGN_NO_MATCHING_EVENTS enum value from the // response property for the response status

      response-property-enum-value-removed

    • ○

      removed the CAMPAIGN_NO_MATCHING_EVENTS enum value from the // response property for the response status

      response-property-enum-value-removed

    • ○

      removed the FIELDS_NOT_FOUND enum value from the // response property for the response status

      response-property-enum-value-removed

    • ○

      removed the FIELDS_NOT_FOUND enum value from the // response property for the response status

      response-property-enum-value-removed

    • ○

      removed the FIELDS_NOT_FOUND enum value from the // response property for the response status

      response-property-enum-value-removed

    • ○

      removed the FIELDS_NOT_FOUND enum value from the // response property for the response status

      response-property-enum-value-removed

    • ○

      removed the FIELDS_NOT_FOUND enum value from the // response property for the response status

      response-property-enum-value-removed

    • ○

      removed the JUDGE_ALREADY_HAS_NEW_VERSION enum value from the // response property for the response status

      response-property-enum-value-removed

    • ○

      removed the JUDGE_ALREADY_HAS_NEW_VERSION enum value from the // response property for the response status

      response-property-enum-value-removed

    • ○

      removed the JUDGE_ALREADY_HAS_NEW_VERSION enum value from the // response property for the response status

      response-property-enum-value-removed

    • ○

      removed the JUDGE_ALREADY_HAS_NEW_VERSION enum value from the // response property for the response status

      response-property-enum-value-removed

    • ○

      removed the JUDGE_ALREADY_HAS_NEW_VERSION enum value from the // response property for the response status

      response-property-enum-value-removed

    • ○

      removed the JUDGE_USED_IN_CAMPAIGN_CANNOT_BE_UPDATED enum value from the // response property for the response status

      response-property-enum-value-removed

    • ○

      removed the JUDGE_USED_IN_CAMPAIGN_CANNOT_BE_UPDATED enum value from the // response property for the response status

      response-property-enum-value-removed

    • ○

      removed the JUDGE_USED_IN_CAMPAIGN_CANNOT_BE_UPDATED enum value from the // response property for the response status

      response-property-enum-value-removed

    • ○

      removed the JUDGE_USED_IN_CAMPAIGN_CANNOT_BE_UPDATED enum value from the // response property for the response status

      response-property-enum-value-removed

    • ○

      removed the JUDGE_USED_IN_CAMPAIGN_CANNOT_BE_UPDATED enum value from the // response property for the response status

      response-property-enum-value-removed

    • ○

      removed the SEARCH_NOT_FOUND enum value from the // response property for the response status

      response-property-enum-value-removed

    • ○

      removed the SEARCH_NOT_FOUND enum value from the // response property for the response status

      response-property-enum-value-removed

    • ○

      removed the SEARCH_NOT_FOUND enum value from the // response property for the response status

      response-property-enum-value-removed

    • ○

      removed the SEARCH_NOT_FOUND enum value from the // response property for the response status

      response-property-enum-value-removed

    • ○

      removed the SEARCH_NOT_FOUND enum value from the // response property for the response status

      response-property-enum-value-removed

    • ○

      removed the SEARCH_SERVICE_UNAVAILABLE enum value from the // response property for the response status

      response-property-enum-value-removed

    • ○

      removed the SEARCH_SERVICE_UNAVAILABLE enum value from the // response property for the response status

      response-property-enum-value-removed

    • ○

      removed the SEARCH_SERVICE_UNAVAILABLE enum value from the // response property for the response status

      response-property-enum-value-removed

    • ○

      removed the SEARCH_SERVICE_UNAVAILABLE enum value from the // response property for the response status

      response-property-enum-value-removed

    • ○

      removed the SEARCH_SERVICE_UNAVAILABLE enum value from the // response property for the response status

      response-property-enum-value-removed

    This revision also has 36 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

    • ●

      added the new OPTIMIZATION_TRIAL_KEY_ALREADY_EXISTS enum value to the // response property for the response status

      response-property-enum-value-added

    • ●

      added the new OPTIMIZATION_TRIAL_KEY_ALREADY_EXISTS enum value to the // response property for the response status

      response-property-enum-value-added

    • ●

      added the new OPTIMIZATION_TRIAL_KEY_ALREADY_EXISTS enum value to the // response property for the response status

      response-property-enum-value-added

    • ●

      added the new OPTIMIZATION_TRIAL_KEY_ALREADY_EXISTS enum value to the // response property for the response status

      response-property-enum-value-added

    • ●

      added the new OPTIMIZATION_TRIAL_KEY_ALREADY_EXISTS enum value to the // response property for the response status

      response-property-enum-value-added

    This revision also has 20 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

  • 933c4ebdcd72111See the full diff
    • ▲

      removed the required property / from the response with the status

      response-required-property-removed

    • ●

      removed the request property /

      request-property-removed

    • ○

      the request property became optional

      request-property-became-optional

    This revision also has 34 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog