New concept of monitoring
April 29, 2020

New concept of monitoring

Anonymous | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User

Overall Satisfaction with ScienceLogic SL1

SL1 is our recommended strategic tool for monitoring. It must be used for all new customers. Its aim is to monitor servers, hardware and to be integrated in a global solution, that is event management, ticketing tools by example. Different strategy could be used to deploy the solution: On-premise, on SL1 cloud or on our cloud.
  • Discovering.
  • New technology.
  • Adaptation.
  • Scheduling.
  • Log monitoring.
  • Message collectors.
  • Not yet estimate.
  • Easy to use and to configure.
  • Easy to manage.
Yes - Old monitoring tool based on old technology. SL1 monitoring offers new capabilities and could cover cloud or hybrid solution by deploying SL1 appliances on premises or on cloud, or by using cloud API to monitor virtual servers. Another point is the agentless monitoring, other old solutions need to deploy agent on target devices.
SL1 is not yet deployed in our customer infrastructure, so it is difficult to have a clear view. Nevertheless we hope that SL1 monitoring could offer more functionalities for all kind of monitoring such as Docker and Kubernetes. We hope also that SL1 could cover all specific monitoring already used by our client.
We need to use and to deploy Docker, Kubernetes for automation purposes. SL1 must be used to monitor Docker and Kubernetes and SL1 must be integrated in automatic workflow used to create or remove virtual servers.
An orchestrator will be used to create or to remove virtual servers, and also to deploy new applications. Through API requests the orchestrator tool could add or remove device in the SL1 scope, it could also stop and restart monitoring, by example for downtimes.
  • Orchestration.
  • Cloud.
  • Customization.
Sciencelogic SL1 is a strategic choice for all our customers. So for new customers or for new contracts we must use SL1 solution.
SL1 is well suited for all standard monitoring and discovery. Data collector high availability and scalability by using collector unit group is a good point. But using message collectors could be less appropriate for a huge number of devices to monitor. Recommended sizing for message collector is about 200 devices/message collector appliances.