SnapLogic Public APIs for Pipeline Runtime Execution Info
Created by @cstewart This pipeline uses the SnapLogic Public APIs to read the summary of executions, then does two things with them; first writes the line detail retrieved into a file, and concurrently, also writes a summary into a file, so you can see what the output contains. This pipeline utilizes the following techniques: Using the iteration feature of the REST Get Snap so that the multiple iterative requests required to retrieve the detail from the SnapLogic Public APIs are consumed. Dynamically configuring the URLs used with the expression language ternary operator Using an expression to get the org name (for use in the URLs) Putting multiple different format data into a single output stream, with an implication of order Configuration The REST Get Snap will need a REST Basic Auth account with credentials valid to make the request to the platform, and the result will only include the results for those executions which those credentials have authority to see. Sources: SnapLogic API Targets: CSV and JSON Files Snaps used: REST Get, JSON Splitter, Copy, Aggregate, Mapper, Union, JSON Formatter, CSV Formatter, File Writer Downloads GetRuntimeInfo.slp (19.8 KB)
Get metrics and resource utilization on current Snaplexes
Contributed by @pkona This pipeline pattern uses the APIs from SnapLogic metrics to query all Snaplexes and their current resource utilization. The data collected is saved into a database table. Data collected includes: Memory utilization Number of slots in use Node configurations like memory, CPU, disk space, Java version, etc. Configuration User configured on the REST account should be a SnapLogic admin. Specify the org name in the pipeline parameters. Source: SnapLogic API Target: SQL Server Snaps used: Rest Get, Mapper, JSON Splitter, Copy, Filter, Union, SQL Server Insert. Downloads Pattern - SL Org - Capture Snaplex runtime metrics.slp (38.9 KB)