-
Notifications
You must be signed in to change notification settings - Fork 55
chore: Allow test server to report to BAM #1567
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Asset Size Report
Merging this pull request will result in the following asset size changes:
|
Supportability Metric Usage Changes:No matching changes found Supportability Metrics .md File Changes:supportability_metrics.md was changed? New supportability metrics require changes to supportability_metrics.md, as well as a new PR to Angler. Please ensure an Angler PR is created and linked to this PR. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1567 +/- ##
=======================================
Coverage 88.25% 88.25%
=======================================
Files 203 203
Lines 7755 7755
Branches 1574 1574
=======================================
Hits 6844 6844
Misses 792 792
Partials 119 119
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
||
/** fallback if no override was provided or override outright failed to parse correctly */ | ||
if (!agentConfig) { | ||
agentConfig = { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Really to send harvest, only the application ID & licenseKey are needed. To make this .B easier to use, you shouldn't need the rest of the properties but simply provide those 2.
Test server can report its data to BAM directly from pages.
Overview
The testing server will now support reporting its activity to BAM instead of local network when supplied with the
-B
flag and a file path to a config file (.JSON format) or a JSON string as input.An example config would look like:
These values are most easily obtained by inspecting an existing browser entity in NR1 or using NerdGraph to retrieve the configs for an entity.
This was added to support more easily smoke testing certain features with concurrent changes to a BAM consumer that is deployed to a staging cell.
Related Issue(s)
Testing
try it:
with file path
with json string argument
npm run test-server -- -B '{"licenseKey":"...","applicationID":"...","accountID":"...","agentID":"...","trustKey":"...","beacon":"...","errorBeacon":"..."}'