Collections in Agents?

I want to make an agent that runs the same series of actions on a set of artifacts from different projects.

Feeding these items in one-at-a-time is very time consuming and I do not want to setup an agent for each project. We group these items into Collections in Glean, which pulls in a wide variety of data from different sources.

My hope was to feed [[collection]] into an agent as a parameter for the agent to perform the same tasks for different projects, but it cannot be inserted as a Document and when added @collection as Text it does not read any of the content in the collection.

My question:
Is it possible to dynamically select a Collection to run in an agent?

Find more posts tagged with

Glean Agent

Accepted answers

All comments

kzook

Hello! So you cannot directly tag a collection, but you can specify that a collection should be retrieved by using the 'company search' action within the Glean Agent builder. If you toggle this company search step to manual, you can specify an internal collection you've created with, 'collection: xyz123'.

This instructs the agent to search for collections that are named as such internally. I know this isn't a direct way to tag collections, but it is something that works most of the time and clearly shows retrieval of information from named collections.

Hope this helped!

m_stephan

This is very helpful! Need to do some more testing, but it looks like you can filter via [[input]] from the agent top menu so this should make things a little easier (instead of editing the agent to different filter sources).

Will need to do some testing but this is a great start - thank you!

The only other question I may have is if there is a way I can see the actual glean indexed docs as well in order to better target filters. Im not sure what data I have access to for that purpose.

Gleanie Kat

@m_stephan - Unfortunately, it doesn't look like our APIs expose the items in the collection 😕

kzook

@m_stephan Kat is correct - you can't see that level of detail directly within collections or the agent builder menu. However, if you have admin rights to your Glean deployment you can access indexed documents from both the console and at the API level to identify what has been crawled, indexed, etc.

Console: Data sources page shows connector health metrics, including total indexed document counts for each source. You can use the verification pane to search for specific documents to see when they were last crawled, indexed, permissions, etc. https://docs.glean.com/administration/about

API: You can look at the data level to see the total number of documents uploaded vs. indexed AND/OR check for single level document permissions and upload status. https://developers.glean.com/api-info/indexing/debugging/datasource-status

Glean is just surfacing what is already within your connected file structures. So if you know a certain document you/your team has created is valuable you can just call that document as a required doc review in your agent steps.

m_stephan

This is very helpful @kzook - Im not an admin but will see if I can get access, Im building a lot of agents for our team and would be very useful.

To your last comment, we have many instances of the same documents (theres about 5 key artifacts per project) and I was hoping to dynamically select the project in a single agent instead of manually setting it for each agent.

Getting Started

Events

Help Center

glean.com