Skip to content
This repository has been archived by the owner on Apr 22, 2020. It is now read-only.

Define a scope for ZMON agent #70

Open
mohabusama opened this issue Apr 23, 2018 · 0 comments
Open

Define a scope for ZMON agent #70

mohabusama opened this issue Apr 23, 2018 · 0 comments
Labels
enhancement zmon-arch Relevant issues. To be tackled during architecture discussions

Comments

@mohabusama
Copy link
Contributor

ZMON agent is currently used to discover Kubernetes resources and Postgresql resources running on Kubernetes. Eventually zmon-aws-agent should be part of this unified agent as well.

The problem about mixing infrastructure discovery with applications/DB discovery is that it leads to:

  • Slower development and release cycles.
  • Bugs and issues that is not fully related to ZMON.

The idea is to define the following:

  • ZMON discovery scope is mainly related to infrastructure discovery.
  • ZMON agent discovery could be extended (one way or another) by external users.
  • ZMON agent should make infrastructure resources available to all extensible solutions.
@rajatparida86 rajatparida86 added the zmon-arch Relevant issues. To be tackled during architecture discussions label Jul 25, 2018
@pitr pitr added the Chore label May 16, 2019
@laceyallyn laceyallyn removed the Chore label Aug 23, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement zmon-arch Relevant issues. To be tackled during architecture discussions
Projects
None yet
Development

No branches or pull requests

4 participants