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

Cherry-pick #22815 to 7.x: Push log level downstream #22985

Merged
merged 1 commit into from
Dec 9, 2020

Conversation

michalpristas
Copy link
Contributor

Cherry-pick of PR #22815 to 7.x branch. Original message:

What does this PR do?

This PR injects log level settings into fleet section of config as discussed in linked issue.
resulting config will look like this

fleet:
  agent:
    id: {agent_id}
    logging:
      level: warning
  api:
    access_api_key: {agent_api_key}
    kibana:
      host: {host_uri}:443
      hosts:
      - {host_uri}
      protocol: https
      timeout: 5m0s
  host:
    id: {host_id}
inputs:
- artifact_manifest:
    artifacts:
      endpoint-exceptionlist-macos-v1:
...so on

Why is it important?

#20756

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.

cc @ph @ferullo

[Ingest Management] Push log level downstream (elastic#22815)
@elasticmachine
Copy link
Collaborator

Pinging @elastic/ingest-management (Team:Ingest Management)

@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 Dec 8, 2020
@michalpristas michalpristas added enhancement needs_team Indicates that the issue/PR needs a Team:* label labels Dec 8, 2020
@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Dec 8, 2020
@botelastic
Copy link

botelastic bot commented Dec 8, 2020

This pull request doesn't have a Team:<team> label.

@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview

Expand to view the summary

Build stats

  • Build Cause: Pull request #22985 opened

  • Start Time: 2020-12-08T13:11:07.179+0000

  • Duration: 18 min 14 sec

Test stats 🧪

Test Results
Failed 0
Passed 1384
Skipped 6
Total 1390

💚 Flaky test report

Tests succeeded.

Expand to view the summary

Test stats 🧪

Test Results
Failed 0
Passed 1384
Skipped 6
Total 1390

@ferullo
Copy link

ferullo commented Dec 8, 2020

Nice thanks! Endpoint has already merged a change to start reading from this location.

Copy link
Contributor

@blakerouse blakerouse left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Backport looks good.

@michalpristas michalpristas merged commit 88200b4 into elastic:7.x Dec 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants