Skip to content
This repository has been archived by the owner on Nov 13, 2019. It is now read-only.

Migrating to galaxia from any monitoring solution #60

Open
ashishjain14 opened this issue Aug 12, 2016 · 1 comment
Open

Migrating to galaxia from any monitoring solution #60

ashishjain14 opened this issue Aug 12, 2016 · 1 comment

Comments

@ashishjain14
Copy link
Contributor

Let us gather some of our thoughts around here across various aspects of migration.

@snyamars
Copy link
Member

Few aspects that need to be considered:

  1. Availability of Non-intrusive connectors for legacy landscape (such as .net microagents, middleware microagents, database microagents, mainframe systems etc,.)
  2. Approach to integrate with existing monitoring solutions ( such as connectors to BMC Patrol, IBM Tivoli, TIBCO Hawk etc,.)
  3. Provide connectors to integrate with IAAS providers such as VMWare, OpenStack
  4. Connectors to other operational platforms like Jenkins, TFS, Bamboo, Documentum, SAP, ETL, Analytics etc,.)
  5. Scripts to translate the existing historical data (from existing monitoring systems) to Galaxia backend
  6. Provide multiple integration strategies (such as agent-less and agent-based) to allow seamless migration from existing monitoring tools
  7. Provide a possibility to integrate with existing UIs/dashboards (while having Galaxia as the backend engine)
  8. Integration support for IDAM systems (as every monitoring system will have RBAC) is important for seamless migration

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

No branches or pull requests

2 participants