And the Swiss, and the reaper, and the dude at the dude – Veliam review
The history of the Veliam IT infrastructure monitoring and management system was described in detail in previous articles (Part 1, Part 2). Now it’s time to introduce you in detail to its capabilities and features.
Features of the Veliam system
To get started, let’s dwell on what basic tasks Veliam can solve. Next, we will discuss its features, and in subsequent articles we will separately analyze each opportunity in detail.
So, the Veliam system includes:
- Monitoring servers, workstations, network equipment and sites. With monitoring, the development of the system began, but did not end there. From the very beginning, the emphasis was on the simplicity of the initial setup and the absence of a long configuration for launching into actual operation. The database is already scanning the network, a ready-made set of metrics, triggers, graphs and notifications (including in telegram).
- Connection to servers, network equipment, user computers in one click. No port forwarding and vpn connections are needed. Everything works through a single Veliam management system, including connecting external users to the company’s internal servers.
- Support service (HelpDesk), in which domain authorization and connection to the user from the ticket are implemented, regardless of where he is located. The main thing is that it is connected to the Veliam system.
Solution Architecture
The Veliam software package works according to the SaaS scheme. The choice of this distribution scheme is primarily due to the desire to simplify the installation, configuration and operation for the end user as much as possible. Almost any advanced computer user can install and launch the system. No need to be a strong specialist in system administration. Qualification of ordinary enikey is suitable.
Sample workflow of Veliam
Conventionally, the structure consists of three main components:
- Cloud Veliam, where all the information received is processed.
- Monitoring server for collecting metrics and connecting to devices in the company’s IT infrastructure ..
- Client partwith which the system is managed.
The presented structure allows you to quickly and easily deploy the system. Further updates will occur automatically. It is not necessary to monitor this separately.
Installation and basic setup
You need to start deploying the Veliam system by registering at personal account. In the future, all interaction with the system will go through it with the help of a client, which will be installed on the computer of the Veliam user. After registration, you need to deploy the monitoring server on the local network.
The Veliam monitoring server must be installed in your infrastructure, which you will monitor and which requires a remote connection. He will communicate with the cloud, passing there all the information collected. This server can be deployed on any modern version of Windows, not necessarily the server edition (save money!).
The monitoring server is deployed using the traditional installer for windows systems. Almost any user can handle it. Next, this server will need to be associated with an account in the cloud.
The final stage of the system deployment is the installation of the Veliam client on the administrator’s computer from which management will be carried out. The client connects to the cloud and takes all the information from it.
Important note on monitoring. It is all built on an agentless model. Windows Management Instrumentation (Wmi), with Linux – connection via Ssh. Thus, to start collecting data, it is enough to perform an automatic network scan, select the nodes to add to monitoring, and specify the credentials to connect to them. The system will do the rest itself. We will examine this point in more detail in a separate article devoted entirely to monitoring.
Thus, the whole process from the start of registration in your account to the launch of the system takes 10-15 minutes. At all stages, it is intuitively clear what to do and do not have to delve deeply into the nuances. Running the system to work, to see and try, is not worth the big effort.
Differentiation of access rights
The Veliam system was designed for a distributed hierarchical management structure with differentiation of access rights. This is directly related to the fact that it was developed initially for the needs of an outsourcing company. Veliam can be used to manage large distributed information systems.
A traditional approach to manage access based on users, roles, and permissions is applied. You can create a separate user, for example, with access only to processing applications from the helpdesk system. If you have several such users, then create your own role for them.
Setting access rights is very flexible, allowing you to fine-tune access to each component of the system. Another example – you can make a separate role, which will only be allowed to give remote access to employees to the necessary infrastructure.
Tariff Plans
Veliam is charged according to the number of objects added to the monitoring system. Up to 50 objects are included in the free tariff plan. This is enough to manage a small company. So if you are one, you can safely use the system. There are no additional restrictions in the free tariff.
All other 50 objects will be enough to get acquainted and test the system. In the future, it will be possible to choose the appropriate tariff plan. Prices, as you can see, are very affordable. The cost is indicated per month, but in fact the funds are spent every day. So you can pay for a few days.
Who can come in handy
Based on the above functionality, you can get an idea of who Veliam might be useful for. First of all, to organizations where similar functionality has not been implemented by separate, more complex systems. For example, there is no Zabbix for monitoring or Otrs for helpdesk. Moreover, they do not exist precisely because extensive functionality and all the capabilities are not needed, for the implementation, integration and support of which it will be necessary to spend the time of qualified specialists.
You need to understand that Veliam does not solve each of the listed problems in the best way. But it conveniently combines them all into a single system, simplifying management and implementation. Plus, adds some unique features.
Further, we can note those companies that need simple and convenient remote access to internal services. It is this functionality in the form as it is implemented in Veliam that can be considered unique. It is really simple and easy to use, both for system administrators and for end users. If you do not need monitoring and helpdesk, you can use only remote access. There will be separate detailed material on this topic with a description of the work and examples of use.
It is worth noting another key feature of Veliam. The system emphasizes the ease of installation, configuration and management, which does not impose high requirements on the qualifications of staff. All basic functionality works immediately after installation and does not need to be finalized with a file so that you can use it. So I think that separately to the target users of the system can be attributed budget organizations, where the problem of qualification of personnel is quite acute.
Outsourcing companies can be attributed to another category of users who would benefit from the Veliam system. They should be put on the first place in this list, since the Veliam system was originally created by an outsourcing company to organize its work. It is her needs, first of all, that she solves in the best way from the point of view of company management.
To summarize all that has been said, I want to invite you to see and test the Veliam IT infrastructure management system. Due to its ease of implementation, it does not take much time and does not require changes to target systems. At the same time, you can immediately evaluate and try key features, such as convenient remote access and helpdesk with excellent integration in AD and instant connection to the user from the application.
I remind you that on the topic of monitoring, remote access and helpdesk systems, separate detailed posts will be written later. That’s all with us, until we meet again.
