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

[Ingest Manager]: Log are not updated as per log levels applied at Agent logging level on Agents tab. #22986

Closed
dikshachauhan-qasource opened this issue Dec 8, 2020 · 6 comments

Comments

@dikshachauhan-qasource
Copy link

dikshachauhan-qasource commented Dec 8, 2020

Kibana version:
Kibana:8.0.0 snapshot Cloud environment

Elasticsearch version:
Elasticsearch: 8.0.0 snapshot Cloud environment

Host OS and Browser version:
Windows 10, All

Original install method (e.g. download page, yum, from source, etc.):
8.0.0 snapshot Cloud environment

Description:
[Ingest Manager]: Logs are not updated as per log levels applied at Agent logging level on Agents tab.

Preconditions:

  1. Artifacts for 8.0.0 snapshot Agent should be available.
    Link used: https://staging.elastic.co/7.10.1-de6b0b5d/summary-7.10.1.html/elastic-agent-7.10.1-windows-x86_64.zip
  2. 8.0.0 snapshot Cloud environment should be available.
    COMMIT 008c6a0e19a1c9e130152a6082c574057c841f89
    BUILD 38640
  3. Agent must be deployed.

Steps to Reproduce:

  1. Login to Kibana using a super admin account.
  2. Go to Agents. Notice, by default 'info' agent logging level is selected.
  3. Click on Agent logging level. Select 'debug'
  4. Click on Apply changes.
  5. Observe, a confirmation message is displayed.
  6. Now, refresh the page.
  7. Observe, info logs are generated after the debug level is selected at agent logging level

Impacted Test case id:

Actual Result:
Info logs are generated after the debug level is selected at agent logging level.

Expected Result
Only debug level logs should be generated as per verbosity order after debug level is selected at agent logging level.
Verbosity order: Error > Warning > Info > Debug

What's working:
N/A

What's not working:
N/A

Screenshot:
Loglevelerror

@dikshachauhan-qasource
Copy link
Author

@muskangulati-qasource please review

@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Dec 8, 2020
@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Dec 8, 2020
@elasticmachine
Copy link
Collaborator

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

@muskangulati-qasource
Copy link

Reviewed & Assigned to @EricDavisX

@EricDavisX
Copy link
Contributor

Thanks for testing and logging. I think the feature isn't ready to be evaluated yet, this was bad communication from me and the team I think, sorry. For details, I can cite: we had 75% of the UI finished and then afterwards started putting the PRs up to make the Agent and backend align... it should be ready end to end soon.

This one is just merged to 8.0 and has open backports:
#22815

  • so we'll wait on this to test it end to end.

This is relating, and is for bugs for the same feature so we should wait to test until this as well:
https://github.com/elastic/beats/pull/22987/files

@EricDavisX EricDavisX removed the bug label Dec 8, 2020
@dikshachauhan-qasource
Copy link
Author

Hi @EricDavisX

Thank you for the confirmation.
Please let us know whenever the feature is ready to test. We will re-validate them.

Also, we have validated the merged changes for #22815 and has shared our detailed observation under same ticket.

Please let us know if anything else is required from our side.

@dikshachauhan-qasource
Copy link
Author

The feature has been implemented successfully.
Hence closing this out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants