-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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 ServiceName + ApplicationName based server map #10882
Comments
intr3p1d
added a commit
to intr3p1d/pinpoint
that referenced
this issue
Apr 11, 2024
intr3p1d
added a commit
to intr3p1d/pinpoint
that referenced
this issue
Apr 15, 2024
intr3p1d
added a commit
to intr3p1d/pinpoint
that referenced
this issue
Apr 16, 2024
intr3p1d
added a commit
to intr3p1d/pinpoint
that referenced
this issue
Jun 10, 2024
intr3p1d
added a commit
to intr3p1d/pinpoint
that referenced
this issue
Jun 10, 2024
intr3p1d
added a commit
to intr3p1d/pinpoint
that referenced
this issue
Jun 21, 2024
intr3p1d
added a commit
to intr3p1d/pinpoint
that referenced
this issue
Jun 24, 2024
intr3p1d
added a commit
to intr3p1d/pinpoint
that referenced
this issue
Jul 9, 2024
intr3p1d
added a commit
to intr3p1d/pinpoint
that referenced
this issue
Sep 24, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Pinpoint currently stores the statistical data required by servermap at the
agentId
level. (columnName includesagentId
)Bump this up to a larger unit, only use
serviceName + applicationName
, to speed up reading the serverMap data.For now, (maybe from 3.0.0 to 3.1.0), we'll store
"default"
inserviceName
and use it wheneverserviceName
(orserviceId
, etc.) is updated.The text was updated successfully, but these errors were encountered: