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.

Sign up for GitHub

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

Jump to bottom

Enable integrations-next by default in agent-bare.yaml #1531

Merged
merged 3 commits into from
Mar 25, 2022
Merged

Enable integrations-next by default in agent-bare.yaml #1531

merged 3 commits into from
Mar 25, 2022

Conversation

hjet
Copy link
Contributor

@hjet hjet commented Mar 25, 2022

PR Description

This enables integrations-next by default in agent-bare.yaml.

Please note: grafana/alloy#547

Which issue(s) this PR fixes

Notes to the Reviewer

PR Checklist

  • CHANGELOG updated
  • Documentation added
  • Tests updated

@hjet hjet requested a review from rfratto March 25, 2022 16:53
rfratto
rfratto reviewed Mar 25, 2022
View reviewed changes
CHANGELOG.md Outdated Show resolved Hide resolved
@hjet hjet enabled auto-merge (squash) March 25, 2022 17:24
@hjet hjet merged commit 80dace9 into main Mar 25, 2022
@hjet hjet deleted the enable_integrations_next branch March 25, 2022 17:36
@Kirchen99
Copy link

Kirchen99 commented Nov 9, 2022 •
edited
Loading

May I ask why enable integrations-next by default in agent-bare.yaml ? I'm confused because almost everywhere else except this document are using config without this feature.

For example, we deployed grafana-agent in our kubernetes cluster with integrations-next and then we want to monitor the agent. So we tried the configuration in this document but it doesn't work. Because the integrations.agent.enabled is not able to use in integrations-next.

This makes the documents inconsistent.

@github-actions github-actions bot added the frozen-due-to-age Locked due to a period of inactivity. Please open new issues or PRs if more discussion is needed. label Mar 15, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 15, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers

@rfratto rfratto rfratto approved these changes

Assignees
No one assigned
Labels
frozen-due-to-age Locked due to a period of inactivity. Please open new issues or PRs if more discussion is needed.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@hjet @Kirchen99 @rfratto