is_atlas is always false in telemetry

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 1.29.6
    • Affects Version/s: None
    • Component/s: Telemetry Data
    • None
    • Iteration Seoul
    • Not Needed
    • None

      Seems like we broke the is_atlas check in both old and new telemetry with all the recent chances to instance-helper / connection-model. Whereas before the regex that we use all over the place in Compass for this and the one in mongodb-build-info package expects a host with either a port or a trailing slash at the end, we are now mostly checking against hostname (with no port or trailing slashes) in places where the check is performed

      This will probably go away as soon as COMPASS-5146 is implemented, but I'm opening a ticket anyway so that we don't forget to fix this important telemetry regression

              Assignee:
              Unassigned
              Reporter:
              Sergey Petushkov
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: