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

[8.x](backport #42462) Add status reporting for Journald input #42538

Merged
merged 1 commit into from
Feb 3, 2025

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Jan 31, 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


This is an automatic backport of pull request #42462 done by [Mergify](https://mergify.com).

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

(cherry picked from commit 76f4086)
@mergify mergify bot added the backport label Jan 31, 2025
@mergify mergify bot requested a review from a team as a code owner January 31, 2025 15:49
@mergify mergify bot removed the request for review from a team January 31, 2025 15:49
@mergify mergify bot requested review from AndersonQ and VihasMakwana January 31, 2025 15:49
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Jan 31, 2025
@github-actions github-actions bot added the Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team label Jan 31, 2025
@elasticmachine
Copy link
Collaborator

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

@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Jan 31, 2025
Copy link
Contributor Author

mergify bot commented Feb 3, 2025

This pull request has not been merged yet. Could you please review and merge it @belimawr? 🙏

@AndersonQ AndersonQ removed their request for review February 3, 2025 13:06
@belimawr belimawr merged commit 9d1b27c into 8.x Feb 3, 2025
32 checks passed
@belimawr belimawr deleted the mergify/bp/8.x/pr-42462 branch February 3, 2025 21:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport 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.

2 participants