Start the agent when a collector is used - #280
Open
unflxw wants to merge 1 commit into
Open
Conversation
|
Hi @unflxw, We've found some issues with your Pull Request.
|
unflxw
marked this pull request as ready for review
August 27, 2026 16:30
|
Hi @unflxw, We've found new issues for this Pull Request. Please see the main comment on this issue for a list of all current warnings. This comment will not be updated to reflect resolved warnings.
|
Setting `collector_endpoint` replaces the agent, so host metrics, NGINX metrics, StatsD metrics and environment metadata are not reported at all. The collector implements none of them for the application's host: it can report host metrics, but for the host it runs on, which is another machine. The agent now runs alongside the collector, and only the trace, metric and log data moves to the collector. Its OpenTelemetry listener is turned off there, because that data goes to the collector instead and the two default to the same port. The agent no longer decides whether AppSignal starts, so collector mode keeps working where the agent is unavailable, and stopping it no longer waits for it to flush, because what it holds is a minute of host metrics. Most agent options apply again, leaving only those that configure how it handles trace data to warn that they are ignored.
unflxw
force-pushed
the
start-agent-in-collector-mode
branch
from
August 28, 2026 12:08
213843e to
c9b9c61
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Setting
collector_endpointreplaces the agent, so host metrics, NGINXmetrics, StatsD metrics and environment metadata are not reported at
all. The collector implements none of them for the application's host:
it can report host metrics, but for the host it runs on, which is
another machine.
The agent now runs alongside the collector, and only the trace, metric
and log data moves to the collector. Its OpenTelemetry listener is
turned off there, because that data goes to the collector instead and
the two default to the same port. The agent no longer decides whether
AppSignal starts, so collector mode keeps working where the agent is
unavailable, and stopping it no longer waits for it to flush, because
what it holds is a minute of host metrics.
Most agent options apply again, leaving only those that configure how
it handles trace data to warn that they are ignored.
AppSignal for Ruby turns the agent's OpenTelemetry listener off in appsignal/appsignal-ruby#1595.
The documentation for this change is in appsignal/appsignal-docs#199.