/-/reload API call not applying new config state with remote config

sirdidymus commented 1 year ago

What's wrong?

I realise these are BETA features and these issues may be known/in progress.

running agent with flags -enable-features=remote-configs -config.enable-read-api CONFIGFILE="http://{<config file url>}"

Using a remote http config file Making a change to node exporter config and issuing /-/reload API call succeeds. Issuing /-/config API call shows the updated config.

Behaviour of agent does not reflect the config.

Some things do change dynamically, for example adding labels/relabels.

More advanced options, like disabling collectors/adding filesystem or network device exclusions do not apply dynamically. An explicit restart of the agent systemctl restart grafana-agent will make the changes active.

Steps to reproduce

Use remote config file
make changes to node exporter config for example, exclude network device with - netclass_ignored_devices:
issue /-/reload api call to agent.
observe config is loaded with /-/config api call
observe that the agent is not dynamically changing behaviour

System information

Linux fedora 6.2.14-200.fc37.x86_64

Software version

agent, version v0.33.2 (branch: HEAD, revision: 93a15c09)

Configuration

`-enable-features=remote-configs -config.enable-read-api CONFIGFILE="http://{<config file url>}"`

Logs

No response

bkokken commented 10 months ago

Is there any indication whether this will be resolved or perhaps replaced by changing api implementations like agent management?

rfratto commented 2 months ago

Hi there :wave:

On April 9, 2024, Grafana Labs announced Grafana Alloy, the spirital successor to Grafana Agent and the final form of Grafana Agent flow mode. As a result, Grafana Agent has been deprecated and will only be receiving bug and security fixes until its end-of-life around November 1, 2025.

To make things easier for maintainers, we're in the process of migrating all issues tagged variant/flow to the Grafana Alloy repository to have a single home for tracking issues. This issue is likely something we'll want to address in both Grafana Alloy and Grafana Agent, so just because it's being moved doesn't mean we won't address the issue in Grafana Agent :)

grafana / alloy