Add function for verbose post node data #20
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The verbose query parameter is optional when posting node data. Setting it to true will result in 202 Accepted being returned with a response body containing the measurement IDs of the ingested measurements. This is mostly used in testing scenarios when the measurement ID is needed for further test verification. Due to how data ingestion works in the API the returned measurement ID is not guaranteed to exists. Clients should not rely on this in any production use cases.
TomasWahlgren
previously approved these changes
Oct 22, 2021
TomasWahlgren
approved these changes
Oct 22, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The verbose query parameter is optional when posting node data. Setting it to true will result in 202 Accepted being returned with a response body containing the measurement IDs of the ingested measurements.
This is mostly used in testing scenarios when the measurement ID is needed for further test verification.
Due to how data ingestion works in the API the returned measurement ID is not guaranteed to exists. Clients should not rely on this in any production use cases.