We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The aliveness of an agent is now determined by the following logic:
If any of the conditions below are met, it should return true.
Determined from the AgentStatus object:
RUNNING
Range.from
Range.to
Determined from isActiveAgent:
isActiveAgent
isActiveAgentByGcStat
isActiveAgentByPing
Previously, two conditions were connected with and. This resulted in unnecessary overhead. Fix this first, and then improve isActiveAgent.
and
The text was updated successfully, but these errors were encountered:
[pinpoint-apm#11252] Quickly return true if the AgentStatus is runn…
true
f25a5b6
…ing.
[#11252] Quickly return true if the AgentStatus is running.
8dab1e1
[pinpoint-apm#11252] Limit query to one row for faster response
23b0343
5967edb
[#11252] Limit query to one row for faster response
d9a4836
intr3p1d
No branches or pull requests
The aliveness of an agent is now determined by the following logic:
If any of the conditions below are met, it should return true.
Determined from the AgentStatus object:
RUNNING
Range.from
~Range.to
interval.Determined from
isActiveAgent
:isActiveAgentByGcStat
).isActiveAgentByPing
).Previously, two conditions were connected with
and
. This resulted in unnecessary overhead.Fix this first, and then improve
isActiveAgent
.The text was updated successfully, but these errors were encountered: