Skip to content

Conversation

@herrBez
Copy link
Contributor

@herrBez herrBez commented Mar 12, 2025

Proposed commit message

Add entry for aerospike/metrics input in agentbeat spec

Checklist

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have made corresponding change to the default configuration files
  • I have added tests that prove my fix is effective or that my feature works
  • I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Disruptive User Impact

This should not have disruptive impact on users

Author's Checklist

How to test this PR locally

Related issues

Use cases

Monitor Aerospike via Elastic Agent, create an (experimental) Aerospike integration

Screenshots

Logs

@herrBez herrBez requested a review from a team March 12, 2025 14:50
@herrBez herrBez requested a review from a team as a code owner March 12, 2025 14:50
@herrBez herrBez requested review from belimawr and rdner March 12, 2025 14:50
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Mar 12, 2025
@mergify
Copy link
Contributor

mergify bot commented Mar 12, 2025

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @herrBez? 🙏.
For such, you'll need to label your PR with:

  • The upcoming major version of the Elastic Stack
  • The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • backport-8./d is the label to automatically backport to the 8./d branch. /d is the digit
  • backport-active-all is the label that automatically backports to all active branches.
  • backport-active-8 is the label that automatically backports to all active minor branches for the 8 major.
  • backport-active-9 is the label that automatically backports to all active minor branches for the 9 major.

@herrBez herrBez added the backport-8.x Automated backport to the 8.x branch with mergify label Mar 12, 2025
@pierrehilbert pierrehilbert added the Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team label Mar 12, 2025
@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Mar 12, 2025
@elasticmachine
Copy link
Contributor

Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane)

@pierrehilbert pierrehilbert added needs_team Indicates that the issue/PR needs a Team:* label Team:Obs-InfraObs Label for the Observability Infrastructure Monitoring team labels Mar 12, 2025
@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Mar 12, 2025
@herrBez herrBez merged commit 3758912 into elastic:main Mar 18, 2025
15 checks passed
mergify bot pushed a commit that referenced this pull request Mar 18, 2025
herrBez added a commit that referenced this pull request Mar 19, 2025
(cherry picked from commit 3758912)

Co-authored-by: Mirko Bez <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport-8.x Automated backport to the 8.x branch with mergify Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team Team:Obs-InfraObs Label for the Observability Infrastructure Monitoring team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants