Introduction
Exporting data involves installing export integration and then creating batch export.
Prerequisites
Create folders in the following cloud storage integrations:
- Amazon AWS S3 bucket storage
- Microsoft Azure Blob
Installing export integrations
Based on your preferences, you can integrate AWS S3 or Azure Blob with OpsRamp. After successful integration, you can create batch export to move data to the respective locations configured in AWS S3 buckets or Azure Blob containers. For more information, see AWS S3 Integration. For more information, see Azure Blob Store Integration.
Creating batch export
Exporting data from OpsRamp to the configured locations in Amazon S3 or Azure Blob Storage is an easy process. You can simply select the desired type of data, schedule the export process as a recurring or on-demand, and select the desired export integration.
Prerequisite
Install export integration for AWS S3 or Blob Storage.
To create the batch export:
- Select Setup > Exports > Batch Export.
- From BATCH EXPORT screen, click +.
- From BATCH EXPORT screen, provide the following information, and click Save & Run.
- Name: Refers to the unique name of the export.
- Client: Refers to the client that requires batch export.
- Type: Refers to the type of data that you want to export.
Note: Usage Batch Export is a Beta feature and has limited historical data. - Schedule: Refers to one of the schedule options to do batch export:
- On Demand Only - Generates exports when a request is created or re-run.
- On-Demand and on Recurring Schedule - Generates export when you raise a re-run request and generates incremental export at scheduled intervals.
- Export to: Refers to the Installed Integration to AWS S3 or Azure Blob.
BATCH EXPORT LIST displays the new export.
Note: When selecting Usage as Type, the option to choose Failure Export Notification is displayed. The email notificiation provides details about the Name, Type, Client, Schedule, Export Destination, Last Run time and date, and Created By.
After creating the batch export, you can:
- Edit: To modify your batch export details.
- Delete: To remove a configured batch export from the OpsRamp platform. Click the Delete icon to remove the batch export.
Notes
- Data is exported in the JSON format.
- The content of the batch export depends on the type and frequency of the batch export schedule. For example, ticket export scheduled at a frequency of one day will have the previous day activity log. A ticket export scheduled weekly or monthly will have the activity log of the previous seven days.
Viewing batch export
After exporting the data from OpsRamp to the installed integrations you can view the exported data in the OpsRamp platform, AWS S3, and Azure Blob.
Attribute | Description |
---|---|
Batch Export Name | Name of the Batch Export |
Client Name | Name of the selected client |
Last Run | The time and date of the recently run export |
Last Export | Displays one of the following status:
|
Created By | Name of the author |
Action | To export data from OpsRamp. The Run Now action is available only for data export with On Demand Only option. |
Viewing batch exports in OpsRamp
You can always view the configured Batch Export details in Exports > Batch Export. The BATCH EXPORT LIST page displays the details of the Batch Export.
Viewing batch exports in AWS S3
You can view the generated batch exports in AWS S3 bucket in the corresponding folders. For example, Alerts export is stored in the Alerts folder.
Export name details
AWS stores the export files in S3 folders as JSON format.
The following list describes the export name in the following screenshot:
- a refers to the schedule of batch export(recurring/on-demand).
- b refers to the Type of batch export.
- c refers to Unique Client ID.
- d refers to the starting timestamp of the schedule.
- e refers to the ending timestamp of the schedule.
- f refers to the serial number of the recurring export.
Viewing batch export in Azure Blob
You can view the generated data exports in the Azure Blob container in the corresponding folders. For example, Alerts export is stored in the Alerts folder.
Export name details
Azure Blob stores the export files in Azure Blob containers as JSON format.
The following list describes the export name in the following screenshot:
- A refers to the schedule of batch export(recurring/on-demand).
- B refers to the type of batch export.
- C refers to Unique Client ID.
- D refers to the starting timestamp of the schedule.
- E refers to the ending timestamp of the schedule.
- F refers to the serial number of the recurring export.