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] Use ML_SYSTEM to detect if agent is running as a service #21884

Merged
merged 3 commits into from
Oct 21, 2020

Conversation

michalpristas
Copy link
Contributor

@michalpristas michalpristas commented Oct 16, 2020

What does this PR do?

We were using SERVICE token to detect whether or not agent is running as a service. But it turned out that in many cases this token is missing.

We decided that it would be better to use ML_SYSTEM which should be close enough to detect high elevated runs == service runs.

Why is it important?

TO make agent upgradeable even on windows.
Fixes: #21822

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.

@michalpristas michalpristas added bug Team:Ingest Management Ingest Management:beta2 Group issues for ingest management beta2 labels Oct 16, 2020
@michalpristas michalpristas self-assigned this Oct 16, 2020
@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 Oct 16, 2020
@elasticmachine
Copy link
Collaborator

elasticmachine commented Oct 16, 2020

💚 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 #21884 updated]

  • Start Time: 2020-10-16T16:08:56.508+0000

  • Duration: 49 min 21 sec

Test stats 🧪

Test Results
Failed 0
Passed 1394
Skipped 4
Total 1398

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.

I have confirmed that this works on Windows 10 with Elastic Agent installed as a service.

@michalpristas michalpristas merged commit 374467e into elastic:master Oct 21, 2020
michalpristas added a commit to michalpristas/beats that referenced this pull request Oct 21, 2020
…vice (elastic#21884)

[Ingest Manager] Use ML_SYSTEM to detect if agent is running as a service (elastic#21884)
michalpristas added a commit to michalpristas/beats that referenced this pull request Oct 21, 2020
…vice (elastic#21884)

[Ingest Manager] Use ML_SYSTEM to detect if agent is running as a service (elastic#21884)
v1v added a commit to v1v/beats that referenced this pull request Oct 21, 2020
…ter-commit

* upstream/master:
  [Ingest Manager] Use ML_SYSTEM to detect if agent is running as a service (elastic#21884)
  Prevent log input from sending duplicate messages due to file renaming (elastic#21911)
michalpristas added a commit that referenced this pull request Oct 22, 2020
…g as a service (#22049)

Cherry-pick #21884 to 7.x: Use ML_SYSTEM to detect if agent is running as a service (#22049)
michalpristas added a commit that referenced this pull request Oct 22, 2020
…ng as a service (#22048)

Cherry-pick #21884 to 7.10: Use ML_SYSTEM to detect if agent is running as a service (#22048)
v1v added a commit to v1v/beats that referenced this pull request Oct 22, 2020
* upstream/master: (27 commits)
  chore: use ubuntu 18 as linux agent (elastic#22084)
  docs: Prepare Changelog for 7.9.3 (elastic#22073) (elastic#22075)
  docs: Prepare Changelog for 6.8.13 (elastic#22072) (elastic#22079)
  [build][packaging] Add resilience when docker build (elastic#22050)
  Fix the url of reviewdog (elastic#21981)
  revert WSS process reporting for windows (elastic#22055)
  Fix typo (elastic#19585) (elastic#22061)
  [Ingest Manager] Use ML_SYSTEM to detect if agent is running as a service (elastic#21884)
  Prevent log input from sending duplicate messages due to file renaming (elastic#21911)
  feat: package aliases for snapshots (elastic#21960)
  [DOC] Add firewall as possible troubleshooting issue (elastic#21743)
  [Filebeat] Add max_number_of_messages config parameter for S3 input (elastic#21993)
  [Elastic Agent] Fix missing elastic_agent event data  (elastic#21994)
  Document auditbeat system process module config (elastic#21766)
  Update links (elastic#22012)
  dynamically find librpm (elastic#21936)
  Fix Istio docs (elastic#22019)
  [beats-tester][packaging] store packages in another location (elastic#21903)
  [Kubernetes] Remove redundant dockersock volume mount (elastic#22009)
  [Ingest Manager] Always try snapshot repo for agent upgrade (elastic#21951)
  ...
@EricDavisX
Copy link
Contributor

I've confirmed this on a Win 7 x64 instance of 7.10 BC4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Ingest Management:beta2 Group issues for ingest management beta2
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Agent] Upgradeable Agent issue - 8.0 Agent is not showing as 'upgradeable=true'
4 participants