Comparing v0.62.0...v0.63.0 · prometheus/common (original) (raw)
Commits on Jan 18, 2025
- Configuration menu
Browse the repository at this point in the history - Configuration menu
Browse the repository at this point in the history
Commits on Jan 20, 2025
- feat(promslog): implement reserved keys, rename duplicates
This commit adds support for "reserved" keys, where upon detecting a
duplicate log attribute key, it will rename the key to prevent
collisions/issues with core slog attribute keys in use.
The reserved keys are:
levelsource(for standard slog style)caller(for legacy go-kit style)time(for standard slog style)ts(for legacy go-kit style)
By supporting reserved keys, we allow users of the library to use these
keys for their own supplemental log attributes.
Fixes: #745
Example test output:
=== RUN TestReservedKeys/slog_log_style
time=2025-01-13T18:32:46.508Z level=INFO source=slog_test.go:212 msg="reserved keys test for slog_log_style" logged_level="surprise! I'm a string" logged_source="surprise! I'm a string" logged_time="surprise! I'm a string"
=== RUN TestReservedKeys/go-kit_log_style
ts=2025-01-13T18:32:46.508Z level=info caller=slog_test.go:212 msg="reserved keys test for go-kit_log_style" logged_level="surprise! I'm a string" logged_caller="surprise! I'm a string" logged_ts="surprise! I'm a string" Note: this implementation only technically removes duplicates of our
core reserved keys. If a user adds multiple instances of a reserved key,
the rest get renamed to logged_$key, which means there could be
duplicate attributes with logged_$key. This is mostly to simplify
implementation so we don't need to bother reference counting in the
replace attr function to do things like logged_$key1, logged_$key2,
etc.
Signed-off-by: TJ Hoplock t.hoplock@gmail.com
tjhop authored
Jan 20, 2025
Configuration menu
Browse the repository at this point in the history
2. Configuration menu
Browse the repository at this point in the history
3. Configuration menu
Browse the repository at this point in the history
4. Bump google.golang.org/protobuf from 1.36.1 to 1.36.3 (#751)
Bumps google.golang.org/protobuf from 1.36.1 to 1.36.3.
updated-dependencies:
- dependency-name: google.golang.org/protobuf
dependency-type: direct:production
update-type: version-update:semver-patch
...
Signed-off-by: dependabot[bot] support@github.com
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Configuration menu
Browse the repository at this point in the history
Commits on Jan 28, 2025
Commits on Feb 3, 2025
- promslog: Make AllowedLevel concurrency safe.
Needed for prometheus/prometheus#10352
Also I renamed AllowedLevel and AllowedFormat to Level and Format.
Default level (and String()) is also now 'info' not empty.
It's a breaking change, but I suspect nobody was using those constructs directly, WDYT?
Signed-off-by: bwplotka bwplotka@gmail.com - info is by default, so no need for the set in New
Signed-off-by: bwplotka bwplotka@gmail.com
Signed-off-by: bwplotka bwplotka@gmail.com
Configuration menu
Browse the repository at this point in the history
Commits on Feb 5, 2025
Commits on Feb 9, 2025
Commits on Feb 19, 2025
- build(deps): bump google.golang.org/protobuf from 1.36.3 to 1.36.4 (#756
)
Bumps google.golang.org/protobuf from 1.36.3 to 1.36.4.
updated-dependencies:
- dependency-name: google.golang.org/protobuf
dependency-type: direct:production
update-type: version-update:semver-patch
...
Signed-off-by: dependabot[bot] support@github.com
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Configuration menu
Browse the repository at this point in the history
Commits on Mar 2, 2025
- build(deps): bump google.golang.org/protobuf from 1.36.4 to 1.36.5 (#761
)
Bumps google.golang.org/protobuf from 1.36.4 to 1.36.5.
updated-dependencies:
- dependency-name: google.golang.org/protobuf
dependency-type: direct:production
update-type: version-update:semver-patch
...
Signed-off-by: dependabot[bot] support@github.com
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Configuration menu
Browse the repository at this point in the history
- Configuration menu
Browse the repository at this point in the history - Configuration menu
Browse the repository at this point in the history
Commits on Mar 4, 2025
- model: Clarify the purpose of model.NameValidationScheme (#765)
There is a lot of confusion around this global variable.
Clarify that it is meant to indicate that a project is aware of UTF-8 support, and that those projects should have their own flags to control validation mode.
Signed-off-by: Owen Williams owen.williams@grafana.com
ywwg authored
Mar 4, 2025
Configuration menu
Browse the repository at this point in the history
