-
-
Notifications
You must be signed in to change notification settings - Fork 168
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Added logging support for instances of RestRequest and RestResponse (#…
…613) * Added new fields & instance method LogEntryEventBuilder.setRestResponseDetails() to store info on instances of System.RestResponse * Added new fields & instance method LogEntryEventBuilder.setRestRequestDetails() to store info on instances of System.RestRequest * Added new flexipage sections 'Apex REST Service Request' and 'Apex REST Service Response' in LogEntryRecordPage that conditionally display the new fields for RestRequest and RestResponse * Renamed the existing flexipage sections 'HTTP Request' and 'HTTP Response' to 'HTTP Callout Request' and 'HTTP Callout Response' for clarity * Reduced the max length of several existing long textarea fields to conserve some usage of the per-object limit - previously, these fields were all using the max length of 131072, which is more than what's needed
- Loading branch information
Showing
65 changed files
with
1,840 additions
and
34 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
23 changes: 23 additions & 0 deletions
23
...ain/configuration/customMetadata/LoggerParameter.StoreRestRequestHeaderValues.md-meta.xml
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,23 @@ | ||
<?xml version="1.0" encoding="UTF-8" ?> | ||
<CustomMetadata | ||
xmlns="http://soap.sforce.com/2006/04/metadata" | ||
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" | ||
xmlns:xsd="http://www.w3.org/2001/XMLSchema" | ||
> | ||
<label>Store REST Request Header Values</label> | ||
<protected>false</protected> | ||
<values> | ||
<field>Description__c</field> | ||
<value | ||
xsi:type="xsd:string" | ||
>When set to 'true' (default), Nebula Logger will store the header values of any instance of an RestRequest that is logged using the instance method LogEntryEventBuilder.setRestRequestDetails(). | ||
|
||
When set to 'false', the header values are not stored or referenced by Nebula Logger. | ||
|
||
Regardless of how this parameter is configured, Nebula Logger will still log the header keys of any instance of an RestRequest that is logged - this parameter only controls if the header values are stored.</value> | ||
</values> | ||
<values> | ||
<field>Value__c</field> | ||
<value xsi:type="xsd:string">true</value> | ||
</values> | ||
</CustomMetadata> |
23 changes: 23 additions & 0 deletions
23
...in/configuration/customMetadata/LoggerParameter.StoreRestResponseHeaderValues.md-meta.xml
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,23 @@ | ||
<?xml version="1.0" encoding="UTF-8" ?> | ||
<CustomMetadata | ||
xmlns="http://soap.sforce.com/2006/04/metadata" | ||
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" | ||
xmlns:xsd="http://www.w3.org/2001/XMLSchema" | ||
> | ||
<label>Store REST Response Header Values</label> | ||
<protected>false</protected> | ||
<values> | ||
<field>Description__c</field> | ||
<value | ||
xsi:type="xsd:string" | ||
>When set to 'true' (default), Nebula Logger will store the header values of any instance of an RestResponse that is logged using the instance method LogEntryEventBuilder.setRestResponseDetails(). | ||
|
||
When set to 'false', the header values are not stored or referenced by Nebula Logger. | ||
|
||
Regardless of how this parameter is configured, Nebula Logger will still log the header keys of any instance of an RestResponse that is logged - this parameter only controls if the header values are stored.</value> | ||
</values> | ||
<values> | ||
<field>Value__c</field> | ||
<value xsi:type="xsd:string">true</value> | ||
</values> | ||
</CustomMetadata> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.