[COMPASS-5323] is_atlas is always false in telemetry Created: 25/Nov/21  Updated: 29/Oct/23  Resolved: 19/Jan/22

Status: Closed
Project: Compass
Component/s: Telemetry Data
Affects Version/s: None
Fix Version/s: 1.29.6

Type: Bug Priority: Major - P3
Reporter: Sergey Petushkov Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on COMPASS-5146 Atlas deployment identification can b... Closed
Documentation Changes: Not Needed
Sprint: Iteration Seoul

 Description   

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



 Comments   
Comment by Jessica Sigafoos [ 19/Jan/22 ]

This was resolved by another ticket.

Generated at Wed Feb 07 22:39:11 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.