Universal REST API Fetcher
PremiumUniversal REST API Fetcher provides a generic interface to fetch logs from cloud sources via REST APIs. Cloud sources can have multiple endpoints, and each configured source consumes one device license.
Universal REST API Fetcher Component:
- Fetcher
- UniversalRestApi
Release Details
Enhancement
PLUG-18407
When URAF rejects a template in an endpoint's request body or query parameters, the error message now names the unsupported element instead of the generic Invalid template variables.
Bug Fix
PLUG-18214
Update Log Sources didn't apply endpoint query parameters from a newer log source template, but the log source still showed the new template version. This affected all log sources created from URAF-based templates, such as Microsoft Graph. Endpoint query parameters now follow the template: Update Log Sources replaces them with the template's query parameters, and any query parameters you added manually are removed. After upgrading, note any custom query parameters before you run Update Log Sources, and add them again afterwards if you still need them.
Past Releases
Universal REST API Fetcher v3.6.1 ▾
Bug Fixes
PLUG-17721
The fetcher could stop responding during the TLS handshake when token requests went unanswered, silently stopping log collection until the service was restarted manually.
PLUG-17874
On log sources with multiple endpoints, headers from one endpoint persisted into later requests, causing those requests to fail.
PLUG-18056
Log sources could not be created or updated when the token URL was not DNS-resolvable locally, even with a proxy enabled.
Universal REST API Fetcher v3.6.0 ▾
Enhancements
PLUG-17565, PLUG-17375, PLUG-17374, PLUG-17373
Introduced URAF configuration APIs so you can manage URAF setup through the API instead of relying on manual configuration steps.
These APIs let you:
Create a URAF log source configuration
Update an existing URAF log source configuration
List URAF log sources and retrieve their details
Delete URAF log sources
Upload the certificate file if the API server uses self-signed SSL certificates
PLUG-17233
Certificates and keys are now stored more securely, with no changes required to the existing configuration.
Bug Fix
PLUG-17503
Requests with
Content-Type: application/x-www-form-urlencoded failed due to incorrect request body construction, which could block URAF API calls in some configurations.Universal REST API Fetcher v3.5.0 ▾
Enhancements
PLUG-16554
You can now upload a custom SSL certificate when configuring URAF for secure, encrypted communication.
PLUG-16614
URAF now supports Token Based authorization type.
Universal REST API Fetcher v3.4.0 ▾
Enhancement
PLUG-16520
URAF now supports link-based pagination, allowing users to fetch logs from sources that send pagination links in their response headers.
Bug Fix
PLUG-16671
While configuring endpoints, users could not send multiple query parameters with the same key, causing problems while fetching logs from APIs that require repeated parameters.
Universal REST API Fetcher v3.3.0 ▾
Enhancements
PLUG-16328
URAF now supports relative URLs for Next Page requests in response headers for consistent log fetching.
PLUG-16293, PLUG-16327
URAF now parses unique JSON Content-Types, for example: application/hal+json for improved compatibility with APIs.
Comments
Article is closed for comments.