The Lyftron Provider for Bugzilla offers the most natural way to access Bugzilla data from Lyftron with ease and also enables to connect with BI, MDM & ML tools, Data warehouses, Databases and other SAAS based applications with zero code and zero infrastructure requirements. The provider wraps the complexity of accessing Bugzilla data into easy-to-integrate relational fully managed ANSI Sql format. Make faster and better business decisions with Lyftron’s Bugzilla data provider and automatically build your data migration pipelines in minutes, not months
The provider hides the complexity of accessing data and provides additional powerful security features, smart caching, batching, socket management, and more.
- Comprehensive Delta load mechanism.
- Real-time access to Bugzilla.
- Comprehensive full support of ANSI Sql to query data with ease.
- Collaborative query processing.
The user must have credentials for Bugzilla, Lyftron and your destination data warehouse, lake or database to perform the data pipeline operation with Lyftron
Establishing a Connection with Lyftron's Quickstart Steps
Create your Bugzilla connection with Lyftron by following the 5 easy steps show below:
Step1. Add your connection
Click on Connect section on the left panel → Click on Add Connection button
Step2. Select your connector
In the connector selection panel, search and click Bugzilla for your connection
Step3. Enter your connection details
In the Connection String section enter the values of the below parameters. The following connection string is required to establish Bugzilla connection with Lyftron.
|Connection Name||Enter your connection details||Required|
|URL||Your Bugzilla domain name||Required|
|APIKey||Your Bugzilla API key||Required|
|Logfile**||Use the logfile option to debug your job and provide your connection name to generate the log file. [ConnectionConfigurationPath]\Connection_name_log.tx||Optional|
|Verbosity**||Choose verbosity 1-5 based on the severity of debugging||Optional|
** For more information, check the Lyftron logging and debugging section.
Step4. Test your connection
Once you are done entering your connection details, simply click on the Test Connection button to test the connectivity. In case your connection fails, add Logfile and Verbosity parameters and check the Lyftron logging and debugging section, to debug the error.
Step5. Save your connection
The Lyftron Provider for Bugzilla models Bugzilla objects as relational tables and views. A Bugzilla object has relationships to other objects in the tables, and these relationships are expressed through foreign keys.
The following sections show the available API objects and provide more information on executing SQL to Bugzilla APIs.
Schemas for most database objects are defined in simple, text-based configuration files.
The provider offloads as much of the SELECT statement processing as possible to the Bugzilla APIs and then processes the rest of the query in memory.
Views are composed of columns and pseudo columns. Views are similar to tables in the way that data is represented; however, views do not support updates. Entities that are represented as views are typically read-only entities. Often, a stored procedure is available to update the data if such functionality is applicable to the data source.
Queries can be executed against a view as if it were a normal table, and the data that comes back is similar in that regard.
|Attachments||Get data about attachments, given a list of bugs and/or attachment IDs. Private attachments will only be returned if you are in the appropriate group or if you are the submitter of the attachment.|
|BugCcDetail||Returns details of the CC of a certain Bug. The 'SELECT * FROM BugCcDetail' query could be slow if you have a lot of Bugs. In that case, use 'IN' filtering for better performance.|
|BugFields||Get information about valid bug fields.|
|BugHistory||Returns information on the history of the bug you specified. The 'SELECT * FROM BugHistory' query could be slow if you have a lot of Bugs. In that case, use 'IN' filtering for better performance.|
|Bugs||Get information about your bugs.|
|Comments||Allows you to get data about comments, given a bug ID or comment ID.|
|CommentTags||Get information about the tags currently set for a comment.|
|ComponentFlagTypes||Get information about the flag types of a component.|
|Flags||Get information on either the flags of an attachment or the flags of a bug.|
|Groups||Returns information about Bugzilla groups.|
|ProductComponents||Get information on the components of a product. Querying 'SELECT * FROM ProductComponents' could be slow because it retrieves all ProductIDs and then makes separate calls for each of them to get the ProductComponents. In that case use 'IN' filtering for better performance.|
|ProductMilestones||Get information about milestones of a certain product. Querying 'SELECT * FROM ProductMilestones' could be slow because it retrieves all ProductIDs and then makes separate calls for each of them to get the ProductMilestones. In that case use 'IN' filtering for better performance.|
|Products||List the available products and get information about them. By default this view will retrieve all accessible and selectable products. If you want to get only the products you can enter bugs against, you must use the 'type' filter like this: type='enterable'|
|ProductVersions||Allows you to get information about versions of a certain product. Querying 'SELECT * FROM ProductVersions' could be slow because it retrieves all ProductIDs and then makes separate calls for each of them to get the ProductVersions. In that case use 'IN' filtering for better performance.|
|Users||Allows you to get information about user accounts.|
To view a detailed advanced settings options, go to Bugzilla Advanced Settings. Complete list of the parameters you can configure in the connection string can be found by clicking Connection String Parameters.