Replace AWS RUM with Client Metrics Server#1672
Open
camillecroci wants to merge 9 commits intomainfrom
Open
Conversation
camillecroci
force-pushed
the
update-client-metrics-web
branch
2 times, most recently
from
7d0369c to
1c7690f
Compare
added 8 commits
February 12, 2026 14:42
We remove everything that is specific to the package: - the dependency - aws* options that were only needed by AWS RUM - isAvailable method was also very specific to RUM - the sample is now done on the server directly - we also remove the record error because its just a firehose of all errors on a page We will encourage people to actually create error events if they want to monitor something in particular
We now accept to just have , but also because we're way more cool now
We now use POST to the client-metrics-server to record events We have the possibility to set the test or prod servers We no longer inforce com.ft. to start a namespace
It is possible to have the home page running locally using ft.com hostname In that case (as its local) we want to send the metrics to our test server So need that edge case in our allowedHostnamePattern
The same check exists in the client server so instead of letting people potentially set a wrong system code in the client and then having the server fail, we reinforce the rule here too. We also emphasize in the README that a wrong system code will stop the client from being instanciated.
camillecroci
force-pushed
the
update-client-metrics-web
branch
from
1c7690f to
16df5e1
Compare
camillecroci
changed the title
camillecroci
requested review from
a team,
ft-dependency-auto-merger and
next-team
as code owners
We created a new domain for it so now we can use that instead of the hako app
camillecroci
force-pushed
the
update-client-metrics-web
branch
from
1b144a3 to
07c4e64
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What
We are replacing AWS RUM with our own Client Metrics Server, which is using Vector under the hood.
So we need to adapt the code to use that new server
What are the big changes?
*.ft.com, we now direct them to our test server (including requests from local.ft.com). The production requests will go to our production server.What are the medium changes
Note (to discuss)
The JIRA ticket example specifies
serverHostname: 'client-metrics.ft.com' // defaultBut I do find is strange to be able to set the client metrics server.
I think when developing locally, people should send their metrics to the test and in prod, it should be production. On staging, send it to test. So I don't think this should be a given option to user.
I may need to add staging.ft.com to the exceptions of
allowedHostnamePatternand maybe rename that variable to make it clearer