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

Add status reporting for Journald input #42462

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

belimawr
Copy link
Contributor

@belimawr belimawr commented Jan 28, 2025

Proposed commit message

This commit adds the status reporting for the Journald input. It also adds a debug log to the UpdateStatus function from v2.Context.

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
## Author's Checklist

How to test this PR locally

  1. Build the Elastic-Agent with Beats from this PR or build Agent beat and replace its binary in a existing Elastic-Agent installation
  2. Create a policy with "Custom Journald logs" or add the integration to an existing policy
  3. Set the log level to debug
  4. Deploy/Restart the Elastic-Agent
  5. Look for the debug messages from the logger input.journald:
    • updating status, status: 'Starting', message: 'Starting'
    • updating status, status: 'Running', message: 'Running'
  6. Ensure the Journald integration for your Elastic-Agent shows the status Healthy

Related issues

## Use cases
## Screenshots
## Logs

@belimawr belimawr added skip-ci Skip the build in the CI but linting Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team skip docs-build Skips docs build CI labels Jan 28, 2025
@belimawr belimawr self-assigned this Jan 28, 2025
@belimawr belimawr requested a review from a team as a code owner January 28, 2025 18:30
@belimawr belimawr requested review from rdner and mauri870 January 28, 2025 18:30
@elasticmachine
Copy link
Collaborator

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

@botelastic botelastic bot added needs_team Indicates that the issue/PR needs a Team:* label and removed needs_team Indicates that the issue/PR needs a Team:* label labels Jan 28, 2025
@belimawr belimawr added needs_team Indicates that the issue/PR needs a Team:* label backport-8.x Automated backport to the 8.x branch with mergify labels Jan 28, 2025
@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Jan 28, 2025
@belimawr belimawr force-pushed the 39791-journald-status-reporting branch from 43be8b4 to 9c98d03 Compare January 28, 2025 18:31
@belimawr belimawr removed skip-ci Skip the build in the CI but linting skip docs-build Skips docs build CI labels Jan 28, 2025
This commit adds the status reporting for the Journald input. It also
adds a debug log to the `UpdateStatus` function from `v2.Context`.
@belimawr belimawr force-pushed the 39791-journald-status-reporting branch from 9c98d03 to 5f7b22f Compare January 28, 2025 18:33
Rename method receiver to fix lint warnings
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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Journald] Implement status reporting for Elastic-Agent
2 participants