Skip to content
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

Introduce a “campaign” label in (some) Prometheus exports #214

Open
scy opened this issue Oct 20, 2023 · 0 comments
Open

Introduce a “campaign” label in (some) Prometheus exports #214

scy opened this issue Oct 20, 2023 · 0 comments
Labels
area:backend Related to the server component class:newcomer Good for newcomers to the project: easy and/or limited scope prio:C Nice to have, but optional type:enhancement New feature or request

Comments

@scy
Copy link
Collaborator

scy commented Oct 20, 2023

It could be useful to track which campaign spent the most money, or made the most calls, or the longest ones, etc.

As with #213, my recommendation would be to base this on the Referer header, but only use the domain, in order to keep the cardinality low. (So that we don’t track which exact page on the campaign’s site is being used.) This is especially important because some campaigns might have tracking parameters or whatever in their URLs, causing them to change for every request.

@scy scy added type:enhancement New feature or request area:backend Related to the server component prio:C Nice to have, but optional flag:after-2.0 labels Oct 20, 2023
@scy scy added the class:newcomer Good for newcomers to the project: easy and/or limited scope label Dec 15, 2024
@scy scy removed this from the 2.1: improvements to instant calling milestone Dec 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:backend Related to the server component class:newcomer Good for newcomers to the project: easy and/or limited scope prio:C Nice to have, but optional type:enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant