-
Notifications
You must be signed in to change notification settings - Fork 77
Collecting provenance
Provenance metadata is generated by SPADE reporters. An arbitrary number of reporters can be added. The SPADE server integrates the provenance records coming from all of them.
To help a user start sending provenance information to SPADE with minimal effort, we have implemented a DSL
reporter. It creates a named pipe in the filesystem, to which a user can send provenance information in a simple language.
It is also possible to report provenance information through a programming interface instead of the DSL
reporter.
We provide additional reporters for collecting operating system level or filesystem level provenance on both Mac OS X and Linux.
To learn more about these reporters, see the submenu items on the left.
Note that the Reporter
class is loaded by and runs as part of the SPADE server. Hence implementing such a class requires handling the inter-process communication with the source from which the provenance is being collected.
This material is based upon work supported by the National Science Foundation under Grants OCI-0722068, IIS-1116414, and ACI-1547467. Any opinions, findings, and conclusions or recommendations expressed in this material are those of the author(s) and do not necessarily reflect the views of the National Science Foundation.
- Setting up SPADE
- Storing provenance
-
Collecting provenance
- Across the operating system
- Limiting collection to a part of the filesystem
- From an external application
- With compile-time instrumentation
- Using the reporting API
- Of transactions in the Bitcoin blockchain
- Filtering provenance
- Viewing provenance
-
Querying SPADE
- Illustrative example
- Transforming query responses
- Protecting query responses
- Miscellaneous