Rubrik collector
Overview
Rubrik is a software-defined data management platform for physical, virtual and hybrid environments, that simplifies and unifies backup, data protection and instant recovery onsite, in the cloud and at the data centre.
Devo collector features
Feature | Details |
---|---|
Allow parallel downloading ( |
|
Running environments |
|
Populated Devo events |
|
Flattening preprocessing |
|
Data sources
Data source | Description | API endpoint | Collector service name | Devo table | Available from release |
---|---|---|---|---|---|
Audit Logs | Returns all corresponding the audit logs. |
|
|
|
|
Events | Returns all the corresponding event logs. |
|
|
|
|
For more information on how the events are parsed, visit our page.
Flattening preprocessing
Data source | Collector service | Optional | Flattening details |
---|---|---|---|
Audit Logs |
|
| not required |
Events |
|
| not required |
Minimum configuration required for basic pulling
Although this collector supports advanced configuration, the fields required to retrieve data with basic configuration are defined below.
This minimum configuration refers exclusively to those specific parameters of this integration. There are more required parameters related to the generic behavior of the collector. Check setting sections for details.
Setting | Details |
---|---|
| The tenant name to be added in the base url. |
| Client ID for authentication. |
| Client Secret for authentication. |
See the Accepted authentication methods section to verify what settings are required based on the desired authentication method.
Accepted authentication methods
Authentication method | Client Id | Client Secret | Base Url |
---|---|---|---|
Basic Authentication | REQUIRED | REQUIRED | REQUIRED |
Run the collector
Once the data source is configured, you can either send us the required information if you want us to host and manage the collector for you (Cloud collector), or deploy and host the collector in your own machine using a Docker image (On-premise collector).
Collector services detail
This section is intended to explain how to proceed with specific actions for services.
Audit logs
Used Graphql Query
query AuditLogListQuery(
$after: String
$first: Int
$filters: UserAuditFilter
$sortBy: UserAuditSortField
$sortOrder: SortOrder
) {
userAuditConnection(
after: $after
first: $first
filters: $filters
sortBy: $sortBy
sortOrder: $sortOrder
) {
edges {
node {
userNote
userName
id
message
time
severity
status
cluster {
id
name
timezone
__typename
}
orgId
orgName
__typename
}
cursor
__typename
}
pageInfo {
endCursor
hasNextPage
hasPreviousPage
__typename
}
__typename
}
}
Events
Used Graphql Query
query EventSeriesListQuery(
$after: String
$filters: ActivitySeriesFilter
$first: Int
$sortBy: ActivitySeriesSortField
$sortOrder: SortOrder
) {
activitySeriesConnection(
after: $after
first: $first
filters: $filters
sortBy: $sortBy
sortOrder: $sortOrder
) {
edges {
cursor
node {
...EventSeriesFragment
cluster {
id
name
status
timezone
__typename
}
activityConnection(first: 1) {
nodes {
id
message
__typename
}
__typename
}
__typename
}
__typename
}
pageInfo {
endCursor
hasNextPage
hasPreviousPage
__typename
}
__typename
}
}
fragment EventSeriesFragment on ActivitySeries {
id
fid
activitySeriesId
lastUpdated
lastActivityType
lastActivityStatus
objectId
objectName
objectType
severity
progress
isCancelable
isPolarisEventSeries
location
effectiveThroughput
dataTransferred
logicalSize
organizations {
id
name
__typename
}
clusterUuid
clusterName
__typename
}
Collector operations
This section is intended to explain how to proceed with specific operations of this collector.
Change log
Release | Released on | Release type | Details | Recommendations |
---|---|---|---|---|
| Sep 4, 2024 | IMPROVEMENTS | Improvements
|
|
| Mar 6, 2024 | IMPROVEMENTS | Improvements
|
|
| Mar 6, 2024 | IMPROVEMENTS | Improvements
|
|
| Mar 6, 2024 | BUG FIX |
|
|
| Mar 3, 2024 | BUG FIX |
|
|
| Feb 28, 2024 | FIRST RELEASE | Released the first version of the Rubrik collector. |
|