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

Dialogue DNS logging provides higher signal with less noise #2191

Merged
merged 3 commits into from
Mar 8, 2024

Conversation

carterkozak
Copy link
Contributor

==COMMIT_MSG==
Dialogue DNS logging provides higher signal with less noise
==COMMIT_MSG==

@changelog-app
Copy link

changelog-app bot commented Mar 8, 2024

Generate changelog in changelog/@unreleased

What do the change types mean?
  • feature: A new feature of the service.
  • improvement: An incremental improvement in the functionality or operation of the service.
  • fix: Remedies the incorrect behaviour of a component of the service in a backwards-compatible way.
  • break: Has the potential to break consumers of this service's API, inclusive of both Palantir services
    and external consumers of the service's API (e.g. customer-written software or integrations).
  • deprecation: Advertises the intention to remove service functionality without any change to the
    operation of the service itself.
  • manualTask: Requires the possibility of manual intervention (running a script, eyeballing configuration,
    performing database surgery, ...) at the time of upgrade for it to succeed.
  • migration: A fully automatic upgrade migration task with no engineer input required.

Note: only one type should be chosen.

How are new versions calculated?
  • ❗The break and manual task changelog types will result in a major release!
  • 🐛 The fix changelog type will result in a minor release in most cases, and a patch release version for patch branches. This behaviour is configurable in autorelease.
  • ✨ All others will result in a minor version release.

Type

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

Description

Dialogue DNS logging provides higher signal with less noise

Check the box to generate changelog(s)

  • Generate changelog entry

Comment on lines +114 to +124
@Unsafe
@Nullable
static String tryGetHost(@Unsafe String uriString) {
try {
URI uri = new URI(uriString);
return uri.getHost();
} catch (URISyntaxException | RuntimeException e) {
log.debug("Failed to parse URI", e);
return null;
}
}
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Extracted from a lambda in DialogueDnsResolutionWorker to reuse within describeHostname. There's a similar method in ReloadingClientFactory which doesn't share this implementation because it's where we provide higher priority logging and metrics for invalid URIs -- we don't want to duplicate that N times for a single failure.

@@ -186,7 +186,7 @@ public <T> T getNonReloading(Class<T> clazz, ServiceConfiguration serviceConf) {
Channel channel = new LiveReloadingChannel(
DnsSupport.pollForChanges(
params.dnsNodeDiscovery(),
DnsPollingSpec.SERVICE_CONFIG,
DnsPollingSpec.serviceConfig(channelName),
Copy link
Contributor Author

Choose a reason for hiding this comment

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

I updated these so that we'll get more specific metric tags describing ongoing work, and used the info within the background DNS polling task failure logging so we don't have to guess about the unsafe URI.

@bulldozer-bot bulldozer-bot bot merged commit 22d87cd into develop Mar 8, 2024
6 checks passed
@bulldozer-bot bulldozer-bot bot deleted the ckozak/dns_logging branch March 8, 2024 21:16
@svc-autorelease
Copy link
Collaborator

Released 3.121.0

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

Successfully merging this pull request may close these issues.

4 participants