Skip to content
This repository has been archived by the owner on Nov 14, 2024. It is now read-only.

[Correctness Logger] Part 1b: Namespace Logs Correctly #5604

Merged
merged 4 commits into from
Aug 19, 2021

Conversation

jeremyk-91
Copy link
Contributor

Goals (and why):

  • Don't pollute the global namespace of 'timestampViolations'

Implementation Description (bullets):

  • Change generated metric to use the 'com.palantir.atlasdb.correctness' namespace

Testing (What was existing testing like? What have you done to improve it?):
none

Concerns (what feedback would you like?):
not much

Where should we start reviewing?:
+1-1

Priority (whenever / two weeks / yesterday): ASAP please 🔥

@changelog-app
Copy link

changelog-app bot commented Aug 19, 2021

Generate changelog in changelog/@unreleased

Type

  • Feature
  • Improvement
  • Fix
  • Break
  • Deprecation
  • Manual task
  • Migration

Description

Correctness metrics are now generated under the com.palantir.atlasdb.correctness namespace. Previously, they were generated under a generic timestampViolations top-level namespace.

Check the box to generate changelog(s)

  • Generate changelog entry

@sudiksha27
Copy link
Contributor

👍🏼

@bulldozer-bot bulldozer-bot bot merged commit 45bb6c3 into develop Aug 19, 2021
@bulldozer-bot bulldozer-bot bot deleted the jkong/cl-1-bug branch August 19, 2021 17:19
@svc-autorelease
Copy link
Collaborator

Released 0.396.0

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants