EV Observe - Concepts

Last modified on 2022/10/14 20:12

Companies and sites

     Open url.png See Find out more

  • You can use EV Observe to monitor internal companies as well as customer companies.
  • An internal company, also known as a root, includes internal users, e.g. IT Department or production teams.
    • It can have different sites (multi-site company) that will inherit the same set of configuration rules defined for the root.
  • A customer company is monitored by managed service providers in an MSP or multi-customer context.
    • It contains all of the customer's IT assets to be monitored, i.e. infrastructure facilities management.
    • It can have different sites that will inherit the same set of configuration rules defined for the root.
  • There may also be customer companies that have purchased the solution from MSP resellers.
    • These customer companies manage their monitoring autonomously, without any MSP.
    • Their scope is completely isolated and no inheritance mechanism is enabled.
  • Visibility rules and access rights are applied to each of the companies in order to configure and manage monitoring.

Box

     Open url.png See Find out more

  • The Box is a data collector deployed on internal or customer sites, as close as possible to the monitored scope. It is systematically associated with a company or site.
  • A Box performs the following:
    • Run controls to collect and report monitored data from the monitored hosts.
    • Send notifications as regards the monitored host and services by email or SMS to the relevant users.
  • It can be deployed as a virtual machine or physical machine, i.e. a Box provided by EasyVista.

Hosts

     Open url.png See Find out more

  • These are the information system components to be monitored.

    example  Routers, physical servers, storage arrays, virtual machines (VM)

  • They are grouped in categories.

    example  Wi-Fi base stations, cameras, printers, UPS

  • They are associated with host templates, each of which is associated with a set of service templates. The host templates available depend on the host categories.

    example 

    • The Production Mail Server host is associated with the Windows Server and Exchange Server host templates.
    • When you set up monitoring for a host, this automatically deploys the controls required for its monitoring, e.g. CPU, RAM, inbox availability, etc.
  • The operational state of a host is indicated via different statuses.
    • Status icon - OK.png OK: This indicates that the host is working properly.
    • Status icon - Warning.png Warning: This indicates that the host is operational but requires special attention to anticipate and prevent issues that would change its status to Critical.
    • Status icon - Critical.png Critical: This indicates that the host is not operational.
    • Status icon - Unknown.png Unknown: This indicates that the host status is unknown to monitoring. Its status can be OK, Critical or Warning. You will be required to perform a configuration or administration task.
    • Status icon - Undetermined.png Undefined: This indicates that the host is still unknown to monitoring or that the Box is not reporting the relevant information.
  • The Ping control is implemented by default each time a host is created.

Services

     Open url.png See Find out more

  • Services are associated with hosts.
  • These are control points used to monitor a specific element of the host.

    example  The CPU service reports CPU usage for the associated host.

  • They are based on service templates.
    • By default, they inherit the properties of the associated template.
    • You can adapt their configuration based on your monitoring needs.
  • The configuration of the Box must be updated each time a service is created or modified to ensure that the creation or modification is taken into account.
  • The operational state of a service is indicated via different statuses.
    • Status icon - OK.png OK: This indicates that the service is working properly.
    • Status icon - Warning.png Warning: This indicates that the service is operational but requires special attention to anticipate and prevent issues that would change its status to Critical.
    • Status icon - Critical.png Critical: This indicates that the service is not operational.
    • Status icon - Unknown.png Unknown: This indicates that the service status is unknown to monitoring. Its status can be OK, Critical or Warning. You will be required to perform a configuration or administration task.
    • Status icon - Undetermined.png Undefined: This indicates that the service is still unknown to monitoring or that the Box is not reporting the relevant information.

Service templates

  • Service templates are used to deploy a service for a host. When associated with a host, they facilitate the configuration task by preloading specific information such as predefined arguments or predefined control intervals.

    example  

    • LIN-Cpu service template
    • Predefined arguments: Warning threshold, critical threshold, SNMP community
  • The catalog lists all of the service templates proposed by EV Observe.
    • It is updated by EasyVista.
    • It offers over 1,500 templates and is enhanced with each new version release.
    • It is arranged by service category, e.g. Network, Storage, Servers, Databases, etc., and by publisher.

      example  

      • The LIN-Cpu service template is dedicated to CPU monitoring in a Linux OS.
      • The Docker-Container-Status service template is specific to the monitoring of Docker container status.

User services

  • User services are macro-indicators of the status of services provided to end users by the service provider or the IT Department. They are the building blocks of availability monitoring for SLA purposes, the generation of status pages for non-technical users, and root cause analysis for production teams.

    example  Health status of a remote site, invoicing software or data center

  • A user service comprises hosts and other user services.
    • All of these components have dependencies with the root user service via relationships such as Blocking or Degraded. These relationships have a different impact on the final status.
    • User service status
  • The operational state of a user service is indicated via different statuses. This depends on the status of all of the components of the service.
    • Health icon - OK.png OK: This indicates that the service is working properly.
    • Health icon - Downgraded.png Degraded: This indicates that optimal service is not provided to users, e.g. long response times, multiple short unavailability periods, etc.
    • Health icon - Interrupted.png Down: This indicates that the service is disrupted.
    • Health icon - Unknown.png Unknown: This indicates that the service status is unknown to monitoring. You will be required to perform a configuration or administration task.

Monitoring accounts

  • Monitoring accounts are used by services to query the targeted host.
    • This includes connection information for retrieving the expected data, such as the AD administrator account, read-only SQL Server account or Azure token.
    • They are defined and configured based on a hierarchal structure with different levels, e.g. company > sites > hosts > services. This hierarchy is associated with an inheritance mechanism that reduces repetitive data input and configuration, and facilitates account updates when maintaining a large volume of IT assets.

      example  The domain administrator account is defined only once for the site. It is used for all hosts and for their current and future services.

  • A monitoring account can be adapted and modified for each host or service.
  • Any modification to one of the hierarchy levels of a monitoring account will automatically be propagated to all lower levels, provided no level-specific modifications were defined for one of the lower levels.

Contacts

  • Contacts are the recipients who will receive the notifications and/or reports generated by EV Observe.
    • These may be EV Observe users or non-ServiceNav users.
    • They can be grouped in contact groups.
  • Contacts are automatically created when users are defined in EV Observe. However, you must configure and enable them manually.
  • You can set up a notification policy to notify contacts when specific events occur. This configuration can be adapted to any organization.

    example  On-call time, first escalation contact

Users

  • EV Observe users can be partners or internal users (Coservit Partner Reseller) or MSP customers.
  • Each user is associated with a role that assigns access to specific functions.
Tags:
Powered by XWiki © EasyVista 2022