feat: set is_bff_enabled
custom attribute via logging service; create abstraction to make requests to BFF API endpoints with logError
/logInfo
#1234
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
ENT-9842
DatadogLoggingService
) as a helper to more easily craft queries for BFF-enabled vs. BFF-disabled enterprise customers. For example, in Datadog, the custom attribute should help filter data with@context.is_bff_enabled:{true/false}
vs. hardcoding explicit customer UUIDs via@context.enterprise_customer_uuid:(<uuidA> OR <uuidB>)
.makeBFFRequest
as a helper for the existingfetchEnterpriseLearnerDashboard
, but to make its logic reusable across other non-Dashboard route related BFF endpoints in the future. The primary rationale for this change is to always iterate over any BFF responseerrors
and/orwarnings
, callinglogError
and/orlogInfo
respectively for each. This change should help with observability of the frontend app's interactions with the BFF response data.For all changes
Only if submitting a visual change