Please note that using data injections may entail an extra charge to your usual Devo subscription fee.
Create injections
Data injections allow you to create a new table using data from an already existing table. You can modify and enrich the data as required and inject only the necessary information into the new table, and even send it to a different domain. Data injection may be used, for example, to create a table including only the data you need to work with from a very large table. Tables where data is injected always start with my.app and will include data from the moment you created the injection. Learn more in Special Devo tags.
Data injections are done in real-time. This means that you cannot inject data already in memory; only events that are currently streaming to your Devo domain. The data flow will start from the moment the injection is created.
To perform a data injection:
After the injection has been performed, go to Data Search and select my → app in the finder to access all the tables where you injected data.
Tables where you injected data always have a column named sourceTable that indicates the source table of each event. This information is important when you create a my.app table and inject data from several tables. Learn more about this in the following section.
Inject data from several tables
You can use the data from different tables in your domain and inject it to a single my.app table.
To do it, access one of the tables you want to use, prepare the data as required and inject it to a my.app table following the process explained above. Then, access the rest of the tables you want to use and repeat the process, indicating the same my.app tag levels entered in the first one.
Each of the injections defined will be saved separately in the Injections tab of the Data Management area, so you must name them differently. The only thing that must match is the name of the my.app table that will store the injected data.
In the my.app table generated, the data table from which each event comes from will be indicated in the sourceTable column. The table will include all the columns from the source tables added, and they will show null for events that come from tables where the column does not exist. For example, the capture below shows an injection table with data from the demo.ecommerce.data and siem.logtrust.web.activity tables. In this case, the column bytesTransferred comes from the demo.ecommerce.data table, and the column domain belongs to the siem.logtrust.web.activity table. Checking the sourceTable column, you can see from which table the events come, and the bytesTransferred and domain columns show null if the column does not exist in the source table.
If two or more of the tables used to generate the injection table have a column with the same name, two things may occur:
If the data type of the columns with the same name is the same, they will be merged in a single column. In the following capture, both the demo.ecommerce.data and siem.logtrust.web.activity tables have a column named method and its data type is string in both tables.
If the data type of the columns with the same name is not the same, you will get an error message and the injection will not be created unless you perform the necessary transformations to either make the data type coincide (columns merged) or the column name differs (separate columns).
Manage injections
After injections are created, they appear in the Injections tab of the Administration → Data management area. Check the Injections section to learn how to manage them.