Skip to content

Add :skip_prefix option to allow metrics without configured prefix#3

Merged
BondarenkoStas merged 2 commits intomasterfrom
add-skip_prefix-option
Feb 11, 2026
Merged

Add :skip_prefix option to allow metrics without configured prefix#3
BondarenkoStas merged 2 commits intomasterfrom
add-skip_prefix-option

Conversation

@bautrey37
Copy link

@bautrey37 bautrey37 commented Nov 14, 2025

Adds support for a :skip_prefix option across all metric functions, allowing metrics to be sent without the configured prefix on a per-call basis. Useful for integrating with external systems or sending fully-qualified metric names to services that expect specific naming conventions.

When skip_prefix: true is passed, the configured prefix is omitted from the metric packet. The option works with all metric types and combines with other options like tags and sample_rate.

Will be included in https://github.com/salemove/glia-elixir-utils/pull/56
Which will be included in https://github.com/salemove/wrap-up-assistant/pull/672

QVA-1222

@bautrey37
Copy link
Author

bautrey37 commented Nov 14, 2025

This change is used through the glia Metrics library. https://github.com/salemove/glia-elixir-utils/pull/56

Once merged, I'll have to create the 1.5.1 tag manually.

I haven't tested the changes yet, though these are simple changes. I might need to merge these changes in order for me to use them on the Glia Metrics library so that I can test on an environment to see the metrics.

@bautrey37 bautrey37 marked this pull request as ready for review November 14, 2025 14:51
@bautrey37 bautrey37 requested a review from a team as a code owner November 14, 2025 14:51
@bautrey37 bautrey37 requested review from zidik and removed request for a team November 14, 2025 14:51
Copy link

@zidik zidik left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved on the condition that the comments are addressed

@bautrey37 bautrey37 force-pushed the add-skip_prefix-option branch from 6b24019 to c7cdece Compare November 28, 2025 15:30
@bautrey37
Copy link
Author

@zidik I made the changes to your comments, but I'll be dropping this task. I don't have the time to thoroughly test this.

I'll link it to this ticket. https://glia.atlassian.net/browse/QVA-1222

Elixir version support was changed on
ed9b6b6.

Changes for Cabify were added on
9f43f48.

Change in ownership is added on
0edd0fe.
@BondarenkoStas BondarenkoStas force-pushed the add-skip_prefix-option branch 2 times, most recently from 0b6424d to f810627 Compare February 10, 2026 14:01
@BondarenkoStas BondarenkoStas requested a review from zidik February 10, 2026 14:02
@BondarenkoStas
Copy link

Hey @zidik, I rewrote it a bit (functionality didn't change), re-requested a review for a piece of mind :)

@BondarenkoStas
Copy link

Gitleaks Secret Scanning ruleset — Workflows cannot be required from a less visible repository

is expected to fail https://my.slack.com/archives/CHN6UB7UH/p1768233057166119

@bautrey37
Copy link
Author

Thanks @BondarenkoStas Call-router will definitively use this new functionality.

use Mix.Project

@version "1.4.0"
@version "1.5.1"

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@bautrey37

Call-router will definitively use this new functionality.

do you mean to remove GlobalStatix module and instead of no_namespace pass skip_prefix? Yes that's a great idea

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, exactly!

We could make this option as no_namespace, if you prefer.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe this is the reason why call-router is not on Erlang v26.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was thinking to just use it as no_namespace here, it won't be breaking since all the usage is salemove is just true/false with the same intent. But naming wise skip_prefix is right to the point as it's exactly what it does.
What do you think?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like skip_prefix because its clearer.

Also, the term prefix is already used in this metric library.

Adds support for a :skip_prefix option across all metric functions,
allowing metrics to be sent without the configured prefix on a per-call
basis. Useful for integrating with external systems or sending
fully-qualified metric names to services that expect specific naming
conventions.

When skip_prefix: true is passed, the configured prefix is omitted from
the metric packet. The option works with all metric types and combines
with other options like tags and sample_rate.

QVA-1222
Copy link
Author

@bautrey37 bautrey37 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I approve of the changes. Thanks @BondarenkoStas

@BondarenkoStas BondarenkoStas requested a review from a team February 11, 2026 09:37
@BondarenkoStas BondarenkoStas merged commit 593931d into master Feb 11, 2026
1 of 5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

4 participants

Comments