Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: prometheus/common
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v0.64.0
Choose a base ref
...
head repository: prometheus/common
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v0.65.0
Choose a head ref
  • 5 commits
  • 12 files changed
  • 4 contributors

Commits on May 17, 2025

  1. Update common Prometheus files (#789)

    Signed-off-by: prombot <prometheus-team@googlegroups.com>
    prombot authored May 17, 2025
    Configuration menu
    Copy the full SHA
    098669c View commit details
    Browse the repository at this point in the history

Commits on May 27, 2025

  1. Remove otlptranslator package

    Signed-off-by: Arthur Silva Sens <arthursens2005@gmail.com>
    ArthurSens committed May 27, 2025
    Configuration menu
    Copy the full SHA
    1de8cfa View commit details
    Browse the repository at this point in the history
  2. Merge pull request #791 from prometheus/remove-otlptranslator

    Remove otlptranslator package
    ArthurSens authored May 27, 2025
    Configuration menu
    Copy the full SHA
    95acce1 View commit details
    Browse the repository at this point in the history

Commits on Jun 21, 2025

  1. feat(promslog): add Level() method to get slog.Level (#795)

    Adds a `Level()` method to the promslog.Level type. We already expose
    the configured level with the `String()` method, but only in a
    specifically processed format. This means that downstream projects which
    need a true `slog.Level` value need to do shenanigans like we do in the
    blackbox_exporter here[1]. The slog.Level type is really just an int
    behind the scenes, but buys us access to the type's methods, obviously.
    If we want to make this a bit more flexible/"future proof", we could
    instead have the method return an slog.Leveler interface type. I don't
    think it's necessary though, as we'd probably only want to do that if we
    intended to expose access to promslog.Level's internal slog.LevelVar
    (since that also satisfies the slog.Leveler interface), and I don't
    think that's a good idea -- giving direct access would allow users to
    interact with the level var directly, providing an avenue to change
    level configurations outside of promslog's knowledge, resulting in
    unexpected behavior at best and incompatible behavior at worst. I think
    providing access to the value of the level as a proper slog.Level value
    as done here is useful enough on it's own and the safer option.
    
    1. https://github.com/prometheus/blackbox_exporter/blob/f77c50ed7c0f39b734235931e773cf7b5af1fc8a/prober/handler.go#L236-L249
    2. https://pkg.go.dev/log/slog#Level
    
    Signed-off-by: TJ Hoplock <t.hoplock@gmail.com>
    tjhop authored Jun 21, 2025
    Configuration menu
    Copy the full SHA
    7bd5fff View commit details
    Browse the repository at this point in the history

Commits on Jun 22, 2025

  1. feat: Support negative duration in new function ParseDurationAllowNeg…

    …ative (#793)
    
    Signed-off-by: Dmitry Ponomaryov <iamhalje@gmail.com>
    iamhalje authored Jun 22, 2025
    Configuration menu
    Copy the full SHA
    75c3814 View commit details
    Browse the repository at this point in the history
Loading