@@ -71,7 +71,7 @@ Every collector needs the following environmental variables for setup:
-`MAX_REQUESTS_PER_MINUTE`: represents the threshold for the amount of requests that can be sent to `TARGET_URL` in a minute before the collector instance needs to stop sending requests for a brief period of time.
-`ACCESS_TOKEN`: the token that must be set in order for the collector to retrieve data from whatever API might need the token (example: GitLab, Jira etc.).
Finally, there are additional specifics that some of the collectors will need for which you can find more on the [Collector Specifics](collector-specifics) section.
Finally, there are additional specifics that some of the collectors will need for which you can find more on the [Collector Specifics](#collector-specifics) section.
## Environmental Variables needed for the API
The API needs the following environmental variables for the setup:
...
...
@@ -92,7 +92,7 @@ The API needs the following environmental variables for the setup:
The API can enable experimental features by setting the variable name that describes the feature
as true. For example, `FEATURE_XXX="true"`. where `XXX` is the feature name.
## [Collector Specifics](collector-specifics)
## [Collector Specifics](#collector-specifics)
-**GitLab Workflow Collector**: In addition to the setup needed for environmental variables, you will need the following requirements to be met in order to be able to use this collector:
1. Your hosted GitLab's graphql query complexity must be a maximum of 234.
