[SERVER-69628] Standup Metrics Collection Service Created: 13/Sep/22  Updated: 29/Oct/23  Resolved: 13/Oct/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.2.0-rc0

Type: Task Priority: Major - P3
Reporter: Tausif Rahman (Inactive) Assignee: Tausif Rahman (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Participants:

 Description   

There are 3 potential approaches here:
1. Segment: This is an off-the-shelf solution currently used in db-contrib-tool

  • the db-contrib-tool implementation uses hardcoded key values, which may not be acceptable for the SERVER project, because it is a public repo.
  • if we don't use hardcoded key values, we may have to use CorpSecure requires port forwarding (not ideal)

2. Kanopy Service:

  • This is the alternative if Segment does not work out.

3. Atlas Cluster VPC Endpoint:

  • Setting up an Atlas VPC endpoint accessible from the Evergreen VPC removes the need for auth & upholds security.

AC:

  • Metrics Collection service up & running
  • Evergreen Task verifying that the metrics service can be reached from ubuntu workstations


 Comments   
Comment by Githook User [ 12/Oct/22 ]

Author:

{'name': 'Tausif Rahman', 'email': 'tausif.rahman@mongodb.com', 'username': 'trahman1318'}

Message: SERVER-69628 Standup Metrics Collection Service
Branch: master
https://github.com/mongodb/mongo/commit/61ab44c46f6474094648219537c07378f724b578

Generated at Thu Feb 08 06:13:58 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.