Skip to content

Investigation: Access gprd to retrieve metrics on agent counts

relevant issues/discussion threads:

#534676 (comment 2460489897)

https://gitlab.slack.com/archives/CJS40SLJE/p1745249352964359

New UI in the admin section to support mapping ... (#513370 - closed)

Support searching agents based on multiple para... (#536289)

Spike on organization agent authorization mappi... (#536886 - closed)

I could not find a valid template that fits the bill. This also serves as a reference issue to get teleport access to gprd so that we can count the number of cluster agents and cluster agents that can be used to spin up workspaces.

Background

As part of the sync IPM, we attempted to weight Frontend: Query organization cluster agents on ... (#534676 - closed), but ran into questions as to whether we should implement pagination on the dropdown. This would require considerable frontend effort. An alternative option is to not paginate and render all the agents (org mapped and namespace mapped) as we currently do

As part of the sync IPM, we also attempted to weight Support searching agents based on multiple para... (#536289) , which is a backend spin-off to support New UI in the admin section to support mapping ... (#513370 - closed) spike in: Spike on organization agent authorization mappi... (#536886 - closed) . The question here is whether we want to increase the complexity in the backend to support these filters to improve UX when attempting to map agents.

The conclusion we reached was to gather data from gitlab.com to see agent usage, which I have attached in the linked thread. From this data, I have given my own conclusion as to whether the current scale of workspaces would warant the extra pagination and search filters and the greater effort required to implement them.

Edited by Safwan Ahmed