...
Data Source | Description | GitHub API endpoint | Collector service name | Type | Devo table | Available from release | ||||
Collaborators | Information about collaborators. |
|
|
|
|
| ||||
Commits | Commits made in the repository |
|
|
|
|
| ||||
Forks | Forks created in the repository |
|
|
|
|
| ||||
Events | Information about the different events such as resource creations or deletions. |
|
|
|
|
| ||||
Issue comments | Comments made in every issue. |
|
|
|
|
| ||||
Subscribers | Information about the different users subscribed to one repository. |
|
|
|
|
| ||||
Pull requests | Pull requests made in the repository. |
|
|
|
|
| ||||
Subscriptions | Repositories you are subscribed. |
|
|
|
|
| ||||
Releases | Information about releases made in the repository. |
|
|
|
|
| ||||
Stargazers | Information about users who start repositories making them favorites |
|
|
|
|
| Audit | Organization auditory events. | ||
|
|
|
| SSO Authorizations | Single sign-on authorization. |
|
|
|
|
|
Webhooks | Organization created webhooks. |
|
|
|
|
| ||||
Dependabot Alerts | GitHub sends Dependabot alerts when we detect that your repository uses a vulnerable dependency or malware. |
Dependabot alerts - GitHub Docs
|
|
|
|
| ||||
Dependabot Secrets | Lists all secrets available in an organization without revealing their encrypted values. |
Dependabot secrets - GitHub Docs
|
|
|
|
| ||||
Actions | GitHub Actions for a repository. |
|
|
|
|
| ||||
CodeScan | Code scanning is a feature that you use to analyze the code in a GitHub repository to find security vulnerabilities and coding errors. |
|
|
|
|
| ||||
Enterprise Audit
| Enterprise Auditory Events |
REST API endpoints for organizations - GitHub Docs
|
|
|
|
| ||||
Organization Audit | Organization Auditory events |
REST API endpoints for organizations - GitHub Docs
|
|
|
|
|
...
Expand | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
This service lists all workflows that run for a repository in GitHub. All events of this service are ingested into the table Verify data collectionsPuller OutputA successful initial run has the following output messages for the puller module:
After a successful collector’s execution (this is, no error logs were found), you should be able to see the following log message:
Restart the persistenceThis service makes use of persistence. To restart the persistence, the | ||||||||||||
Expand | ||||||||||||
| ||||||||||||
This service gets the audit log (a sequence of activities) for an organization in GitHub. This service starts collecting 90 days back from the moment the persistence is reset. All events of this service are ingested into table
Verify data collectionPuller outputA successful initial run has the following output messages for the puller module:
After a successful collector’s execution (this is, no error logs were found), you should be able to see the following log message. However, it takes a lot of time to reach the end of this service, as it generates a huge amount of events and starts pulling 90 days back:
Restart the persistenceThis service makes use of persistence. To restart the persistence, the |
Expand | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
Code scanning is a feature that you can use to analyze the code in a GitHub repository to find security vulnerabilities and coding errors. This service returns the codescan results for each repository in case it is enabled. Verify data collectionPuller outputA successful initial run has the following output messages for the puller module:
After successful execution of the collector, you should be able to see the following log message:
Restart the persistenceThis service makes use of persistence. To restart the persistence, the |
Expand | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
This service gets a list of collaborators for each repository in GitHub. Verify data collectionPuller outputA successful initial run has the following output messages for the puller module:
After the successful execution of the collector, you should be able to see the following log message:
Restart the persistenceThis service makes use of persistence. To restart the persistence, the |
Expand | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
This service gets a list of collaborators for each repository in GitHub. Verify data collectionPuller outputA successful initial run has the following output messages for the puller module:
After the successful execution of the collector, you should be able to see the following log message:
Restart the persistenceThis service makes use of persistence. To restart the persistence, the |
Expand | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
This service lists all secrets available in an organization without revealing their encrypted values. All events of this service are ingested into table Verify data collectionPuller outputA successful initial run has the following output messages for the puller module:
After the successful execution of the collector, you should be able to see the following log message:
Restart the persistenceThis service makes use of persistence. To restart the persistence, the |
Expand | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
This service returns the Dependabot Alerts for each repository. GitHub generates an alert when a repository uses a vulnerable dependency or malware. All events of this service are ingested into table Verify data collectionPuller outputA successful initial run has the following output messages for the puller module:
After the successful execution of the collector, you should be able to see the following log message:
Restart the persistenceThis service makes use of persistence. To restart the persistence, the |
Expand | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
This service returns the events for each repository. All events of this service are ingested into table Verify data collectionPuller outputA successful initial run has the following output messages for the puller module:
After the successful execution of the collector, you should be able to see the following log message:
Restart the persistenceThis service makes use of persistence. To restart the persistence, the |
Expand | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
This service returns the forks for each repository. All events of this service are ingested into table Verify data collectionPuller outputA successful initial run has the following output messages for the puller module:
After the successful execution of the collector, you should be able to see the following log message:
Restart the persistenceThis service makes use of persistence. To restart the persistence, the |
Expand | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
This service gets the list of issue comments made into a repository in GitHub. All events of this service are ingested into table Verify data collectionPuller outputA successful initial run has the following output messages for the puller module:
After the successful execution of the collector, you should be able to see the following log message:
Restart the persistenceThis service makes use of persistence. To restart the persistence, the |
Expand | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
This service returns the pull request for each repository, and the associate commits for each pull request. All events of this service are ingested into table Verify data collectionPuller outputA successful initial run has the following output messages for the puller module:
After the successful execution of the collector, you should be able to see the following log message:
Restart the persistenceThis service makes use of persistence. To restart the persistence, the |
Expand | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
This service returns the releases for each repository. All events of this service are ingested into table Verify data collectionPuller outputA successful initial run has the following output messages for the puller module:
After the successful execution of the collector, you should be able to see the following log message:
Restart the persistenceThis service makes use of persistence. To restart the persistence, the |
Expand | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
This service returns Single Sign On authorization for all organizations. All events of this service are ingested into table Verify data collectionPuller outputA successful initial run has the following output messages for the puller module:
After the successful execution of the collector, you should be able to see the following log message:
Restart the persistenceThis service makes use of persistence. To restart the persistence, the |
Expand | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
This service returns information about the users who starts each repository, making it a favorite. All events of this service are ingested into table Verify data collectionPuller outputA successful initial run has the following output messages for the puller module:
After the successful execution of the collector, you should be able to see the following log message:
Restart the persistenceThis service makes use of persistence. To restart the persistence, the |
Expand | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
This service returns information about users subscribed to one repository. All events of this service are ingested into table Verify data collectionPuller outputA successful initial run has the following output messages for the puller module:
After the successful execution of the collector, you should be able to see the following log message:
Restart the persistenceThis service makes use of persistence. To restart the persistence, the |
Expand | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
This service returns information about the repositories the user (used to make the pulling) is subscribed to. All events of this service are ingested into table
Verify data collectionPuller outputA successful initial run has the following output messages for the puller module:
After the successful execution of the collector, you should be able to see the following log message:
Restart the persistenceThis service makes use of persistence. To restart the persistence, the |
Expand | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
List of webhooks created by the organization. All events of this service are ingested into table Verify data collectionPuller outputA successful initial run has the following output messages for the puller module:
After the successful execution of the collector, you should be able to see the following log message:
Restart the persistenceThis service makes use of persistence. To restart the persistence, the |
Expand | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
DescriptionThis service gets the audit log (a sequence of activities) for an enterprise in GitHub.
Devo categorization and destinationAll events of this service are ingested into the table Verify data collectionPuller outputA successful initial run has the following output messages for the puller module:
After a successful collector’s execution (this is, no error logs were found), you should be able to see the following log message. However, it takes a lot of time to reach the end of this service, as it generates a huge amount of events and starts pulling 90 days back:
Restart the persistenceThis service makes use of persistence. To restart the persistence, the |
Expand | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
DescriptionThis service gets the audit log (a sequence of activities) for an organization in Github.
Devo categorization and destinationAll events of this service are ingested into table Verify data collectionPuller OutputA successful initial run has the following output messages for the puller module: Note that the
After a successful collector’s execution (this is, no error logs were found), you should be able to see the following log message. However, it takes a lot of time to reach the end of this service, as it generates a huge amount of events and starts pulling 90 days back:
Note that a
Restart the persistenceThis service makes use of persistence. To restart the persistence, the |
...