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

Add socket bind timing metrics #2047

Closed
wants to merge 5 commits into from
Closed

Conversation

amerguy
Copy link

@amerguy amerguy commented Oct 24, 2023

This metric is helpful to understand networking latencies to help guide reducing connect timeouts.

==COMMIT_MSG==
Add socket bind timing metrics
==COMMIT_MSG==

Possible downsides?

@changelog-app
Copy link

changelog-app bot commented Oct 24, 2023

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

Add socket bind timing metrics

Check the box to generate changelog(s)

  • Generate changelog entry

@amerguy amerguy requested a review from carterkozak October 24, 2023 22:29
.clientName(clientName)
.result(ConnectionSocketBind_Result.SUCCESS)
.build();
this.socketBindFailureTimer = DialogueClientMetrics.of(metrics)
Copy link
Contributor

Choose a reason for hiding this comment

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

Nit: let's factor out the three DialogueClientMetrics.of(metrics) into a local variable which we can reuse for each of the three metric instances we register.

Copy link
Author

Choose a reason for hiding this comment

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

done in ca0dd32

carterkozak
carterkozak previously approved these changes Oct 24, 2023
Copy link
Contributor

@carterkozak carterkozak left a comment

Choose a reason for hiding this comment

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

lgtm, thanks!

@carterkozak
Copy link
Contributor

One sec, I need to review this a bit more closely -- I'm not sure it's doing the right thing

Copy link
Contributor

@carterkozak carterkozak left a comment

Choose a reason for hiding this comment

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

I think this currently measures the time it takes to update an AtomicReference. This is the piece we want to measure: SSLConnectionSocketFactory.java#L246 but not this piece: SSLConnectionSocketFactory.java#L260-L264.

@carterkozak
Copy link
Contributor

I can take a closer look tomorrow

@carterkozak
Copy link
Contributor

Closing because #2053 has already merged

@carterkozak carterkozak closed this Nov 1, 2023
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.

3 participants