- In Bleemeo, all entities (users, agents, events, etc.) belong to an account. Accounts are isolated and you can’t move entities between accounts.
- Bleemeo agent or agent
Software running on your server and which is in charge of sending metrics to Bleemeo Cloud platform.
It could also be used to represent the monitored server. You will have one running agent (the software) for each of your monitored servers.
- Bleemeo Cloud platform
- The online part of Bleemeo monitoring solution. Your metrics are stored in this platform which ensures that your data are always available. The visible part of Bleemeo Cloud platform is the panel and the API.
- Bleemeo API
- The API (Application Programming Interface) allows you to query all your data stored by the Bleemeo Cloud platform. From your users to your metrics data, everything may be retrieved/created/deleted. This interface is designed for computer and program, the human friendly interface is the panel.
- Bleemeo have two type of dashboards: default dashboard built when you register an agent that expose all key metrics and information of your server. You can also create custom dashboards with your metrics and mixing data from several agents.
- When something happen on your infrastructure, it creates an event. For exemple when apache stops, an event is created. When apache is started again, another one is created.
- A user can belong to one or several groups. Those groups grant him access to functionalities of the web panel. Check the users management page for more details.
A metric is a named list of values with timestamps. A metric is associated with an agent and may have an item.
The name represents what is monitored, for example cpu_idle (percentage of CPU unused) or disk_used (number of bytes used on the disk).
The item is used when the metric applies to multiple objects, like multiple disks. For example, disk_used has multiple items like “/”, “/home”… When there is only one possible object, item is not set. For example cpu_idle is always associated with the sum of all CPUs or cores.
- You can be notified on events that happen on your infrastructure. You can decide what kind of event, and the servers where the events come from. Notifications can be delivered by mail or SMS. Check the notification documentation page for more details.
- A service running on your machine: Apache, Elasticsearch, etc. We detect a couple of services by default (check our documentation with all autodiscovered services), you can also add custom checks (nagios checks from Monitoring Plugins Website for example). For autodetected services, we are also creating associated metrics that you can graph on your custom dashboards.
- For each person that need to access the UI you can create a user. The username is the user email. Check the user management documentation for more details. Our pricing is not based on your team size. You can add as many users as you want.
- A tag with the name of the service is associated to each server. You can filter using this tag in notifications and other sections of the panel.
A metric can have four thresholds. Check the metric documentation to see the metrics that have default thresholds. You can customize (or set for the metrics that do not have any thresholds) the thresholds. You can define 4 thresholds:
- a low warning
- a low critical
- a high warning
- a high critical