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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use sumologic extension base URL to determine the appropriate OpAMP endpoint #1399
Use sumologic extension base URL to determine the appropriate OpAMP endpoint #1399
Changes from 8 commits
b0e6ccf
b0c67b8
99d0a27
7e00d63
805bdbc
b9e7099
fa7ff75
18555a9
e632091
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I thought we'd agreed to parse the Sumo deployment name out of the domain and explicitly construct a new one. Any reason to do a string replace here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe it's my naivete regarding Sumo deployments, but it seems even more error prone to me. How do I know which deployments correspond to open-events, and which correspond to open-collectors (and correspondingly, opamp-events and opamp-collectors). This knowledge is not encoded anywhere in the codebase, unless I'm mistaken, and I don't know how it would be determined either.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was hoping to do
https://long-open-events.sumologic.net
-> deployment =long
-> constructwss://{{ deployment }}-opamp-events.sumologic.net/v1/opamp
. But looking at it now, these domains are actually different in production environments, so this might be even more complicated.I'm fine with it if we add test cases for all the possible forms of this url. For example, on prod it's just
open-collectors.sumologic.com
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
wss://stag-opamp-events.sumologic.net/v1/opamp
wss://long-opamp-events.sumologic.net/v1/opamp
wss://opamp-collectors.au.sumologic.comt/v1/opamp
wss://opamp-collectors.ca.sumologic.comt/v1/opamp
wss://opamp-collectors.de.sumologic.comt/v1/opamp
wss://opamp-collectors.eu.sumologic.comt/v1/opamp
wss://opamp-collectors.fed.sumologic.comt/v1/opamp
wss://opamp-collectors.in.sumologic.comt/v1/opamp
wss://opamp-collectors.jp.sumologic.comt/v1/opamp
wss://opamp-collectors.sumologic.comt/v1/opamp
wss://opamp-collectors.us2.sumologic.comt/v1/opamp
Open receiver can be found at
https://help.sumologic.com/docs/api/getting-started/#sumo-logic-endpoints-by-deployment-and-firewall-security