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

Grafana Agent - Repo Install #148

Open
ohdearaugustin opened this issue Feb 10, 2024 · 4 comments · May be fixed by #154
Open

Grafana Agent - Repo Install #148

ohdearaugustin opened this issue Feb 10, 2024 · 4 comments · May be fixed by #154

Comments

@ohdearaugustin
Copy link
Contributor

ohdearaugustin commented Feb 10, 2024

As the agent is available in the apt repo and rpm repo.

It would be nice to be able to install the agent from those repos.

PR: For the apt repo working on it.

Tasks

No tasks being tracked yet.
@ohdearaugustin
Copy link
Contributor Author

I think I need to split this into two PRs.

  1. Refactor the setup (to make it easier extendible.)
  2. Add the repo support

I was thinking of about the same structure of the grafana role, but keeping the possibility to install via downloaded binary. (Which devop or sysadmin ever will install software like that.)
@ishanjainn @v-zhuravlev are there any requirements of non breaking changes etc?

@ohdearaugustin ohdearaugustin linked a pull request Feb 14, 2024 that will close this issue
@ohdearaugustin
Copy link
Contributor Author

ohdearaugustin commented Feb 14, 2024

The more I get into the role, the more I'm questioning how that thing even works and the more confused I get.
There are so many issues in installing the agent like that.

  1. It uses a different systemd unit as upstream install via a repo
  2. It does a preflight check if _grafana_agent_system_dir is available?!
  3. It has a loop that install/directories.yaml is executed twice
  4. The download of the binary is made to the localhost (more useful on the host where it is gonna be installed, otherwise you have to upload it to the host again)
  5. Configuration is only working for static agent (config is spliced into several variables)
  6. The role itself is very complex
  7. No tests
  8. Not tested: The role doesn't seem to be idempotent it will always try to install the newest version. It always has to download the binary and overwrite it, even when the version is fixed.
  9. http/grpc ports are different from upstream packages (random port: 12345)
  10. Add support for ansible-playbook serial > 1 (manage multiple hosts at a time) #153
  11. Implement templating of grafana_agent_provisioned_config_file #145

This list is not complete yet I guess.

All of my statement are of course rather opinionated. I'm open to discussion. You can find my progress in the PR.

Maybe we should also discuss if a support for this kind of manual install is still necessary. As it could be quite some work keep it up to date with the package install, which I guess is done by another team within grafana.

Sorry got a bit carried away today haha

@ishanjainn
Copy link
Member

really really looking forward to your final PR 🚀🚀

@voidquark
Copy link
Collaborator

Based on the message in the Grafana Agent documentation:

Grafana Alloy is the new name for our distribution of the OTel collector. Grafana Agent has been deprecated and is in Long-Term Support (LTS) through October 31, 2025. Grafana Agent will reach an End-of-Life (EOL) on November 1, 2025. Read more about why we recommend migrating to Grafana Alloy.

I believe this can be closed, and migration to Alloy is required. @ishanjainn, what are your thoughts?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants