Authorize and start a new collector
Create a collector
To request data from a source, create a collector and provide it with the secrets it needs to make the request.
Open the Cloud Collector App.
Select “Catalog.”
Find the collector.
Contact us if you cannot find the collector in the catalog. Since some collectors are very flexible, it can be difficult to identify all the kinds of data they can collect. For example, the AWS SQS collector and Azure collector can collect all kinds of data from queues.
Select “Create instance.”
Name the collector.
When naming the collector, ensure the name contains sufficient detail to streamline future secret rotation. This is crucial because expired secrets are a primary cause of collector failures.
Edit the parameters.
Change the
id
field to a unique five digit number in quotation marks. For example, if the time is 17:34:22, set the number to 17342 and it will probably be unique. If two collectors have the sameid
, data loss or corruption may occur.
b. For information on how to fill out the other parameters, check the documentation for the specific collector.
c. Ensure the credentials
fields are completed.
d. Leave the debug
field set to false
.
The “Environment variables” are reserved for future development.
Most customers will only need the default keychain. If special event load balancers have been purchased (for example, to meet complex data residency requirements) then uncheck the “Sender configuration” box and select the keychain associated with the correct event load balancer.
Select “Create instance.”
The collector will take up to three minutes to start.
To check the status of the collector:
Get the collector ID from the “Installed collectors” page.
Search for the collector ID in
devo.collectors.out
. An example query isfrom devo.collectors.out where startswith(hostname, "collector-563ae0ff0ba02ef4")
If the data source has data available, go to “Data search” and click the refresh button to see which tables are being populated by all your collectors.
If several collectors are using the same table, the hidden
hostchain
field can be used to identify them. For example,from my.app.test.writer group by split(hostchain,"-",1) as collector_id
After creating a collector, it is helpful to set up monitoring.