Feat: qs api integration connection status #4628
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
raj-k-singh
changed the base branch from
develop
to
feat/qs-integrations-http-api
raj-k-singh
force-pushed
the
feat/qs-api-integration-connection-status
branch
from
8642272
to
3cb8961
Compare
raj-k-singh
force-pushed
the
feat/qs-api-integration-connection-status
branch
from
1d9697b
to
d47349e
Compare
srikanthccv
approved these changes
Mar 5, 2024
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.
Summary
Adds integration connection status HTTP api in query service
See https://www.notion.so/signoz/Integration-V0-UI-Facing-APIs-60c543247c6a432eb9fd69c3376e5602 for details of the expected API contract
Related Issues / PR's
Contributes to #4462
Affected Areas and Manually Tested Areas
QS http API for integrations