




As the saying goes, “no man is an island.” This statement hulds in today’s cybersecurity landscape.



Given the current context, post-covid-19, talking about cloud security with CIEM has become essential. This is because the pandemic motivated the adoption of remote work by most organizations, which resulted in a significant increase in the adoption of cloud-based infrastructure.
As you can imagine, this feature presents particularities when it comes to cybersecurity. To get a sense, Gartner predicts that companies will suffer at least 2,300 violations of privilege policies annually by 2024.
Also according to Gartner, multi-cloud environments introduce a large cyberattack surface that can be exploited by malicious agents. Thus, incorrectly configuring security and identity tools in cloud environments may have violations as a consequence. Therefore, it is not recommended that the settings and maintenance in the access policy be performed manually.
Added to this is the fact that conventional solutions, such as IGA and PAM, may not be efficient to manage this demand. In addition, with infrastructure as a service (IaaS), access management is the responsibility of the client company. According to Gartner, 99% of data breaches occurring in a cloud environment are the responsibility of the customer, not the Cloud Service Provider (CSP).
In this article, we share everything you need to know about cloud security with CIEM. To make our text more understandable, we divided the content by topics. These are:
Follow our text to the end!
In the 1950s, computers were very expensive and companies had access to few machines. For this reason, in the following decade, cloud computing began to be discussed by experts.
The first person to suggest shared use of computers was American computer scientist John McCarthy, who named this concept Utility Computing.
In the following years, Joseph Carl Robnett Licklider studied different ways to use the computer and the Network of Advanced Research Project Agencies (Arpanet), which he helped develop, enabling two or more computers to share data, even in different locations, according to the principles of accessibility and availability.
But the term “cloud computing” was only used for the first time in the second half of the 1990s, in an academic lecture given by the professor of information systems, Ramnath Chellappa. This expression is based on the symbol of the internet: the cloud.
Today, we also have the concept of multi-cloud, which consists of the use of various cloud services. These services can be provided by third-party providers or include a private cloud, whose technology is in the organizations’ own data center.
This type of solution enables IT teams to perform individual operations efficiently, while companies reduce costs.
There is also the hybrid cloud concept, which unites public cloud services with a private cloud, simplifying remote cloud operations and providing more flexibility for businesses.
However, unlike cloud environment management, which must be managed in isolation, hybrid cloud management needs to be based on a unique strategy.
With the evolution of technology, cloud computing has become accessible, and remote work, adopted by many organizations after the beginning of the covid-19 pandemic, has made this resource widely used.
The big issue is that the larger the company, the more people will have access to cloud-based environments. Moreover, many permissions are granted to applications and machines that connect to other applications and databases to exchange information.
Thus, it is necessary to have a strategy that limits unnecessary access and prevents inadequate sharing of information, which can be achieved through CIEM.
Cloud Infrastructure Entitlements Management (CIEM) has the function of managing access in cloud and multi-cloud environments.
This is possible through the access principle of least privilege, which contributes to companies that need to avoid risks such as attacks by malicious users and information leaks, problems generated by excessive permissions on this type of infrastructure.
Thus, a CIEM solution allows you to remove these excessive permissions and centralize the visibility and control of permissions of a cloud environment.
Through the use of artificial intelligence, a CIEM solution is also able to analyze exposure levels of a company’s cloud environments, enabling the identification and reduction of cybersecurity risks.
. Why Are CIEM Solutions Important?
Using cloud resources is very beneficial for businesses, as it allows them to simplify their operations and save time.
However, traditional identity and access management (IAM) tools are aimed at protecting static applications and structures rather than cloud infrastructure, which is extremely dynamic.
So, cloud providers have launched their own resources to ensure cybersecurity in this type of environment. Despite this, the dynamism and diversity of cloud environments continue to pose challenges to ensure data protection and compliance with security policies.
After all, it is necessary to keep in mind that when a company uses the cloud to become more efficient, it can increase its attack surfaces with the excess of permissions in that environment. To make things worse, in such cases, it may not have the visibility and control necessary to apply the principle of least privilege.
In this sense, CIEM solutions are essential to improve visibility, identify and correct incorrect access-related settings with minimal privileges in cloud and multi-cloud infrastructures, and thus ensure the organization’s cybersecurity.
A CIEM solution can generate several benefits for an organization. Check out the main ones below:
In the following topic, we approach these benefits from another perspective: by showing how CIEM can be used to ensure more cybersecurity for companies.
Good IT security requires discovering and classifying identities and recognizing permissions granted to people and machines in order to prevent data leaks and breaches. In this sense, CIEM can be used to:
CIEM enables continuous monitoring of identities and permissions, including changes in rights;
For DevOps teams, managing cloud computing while maintaining information security can be challenging, after all, their priorities are speed and innovation rather than security.
This is because the services must be launched or provisioned with agility, which ends up causing an excessive granting of permissions. However, the manual blocking of these rights is complex and compromises the fundamental speed for this type of operation.
With CIEM, one can eliminate excessive permissions automatically, without interrupting developers, who can deploy code quickly and securely.
Check out the advantages of contracting the senhasegura CIEM service below:
By reading this article, you saw that:
Did you like our article on CIEM solutions? Share it with someone who can benefit from this knowledge.
ALSO READ IN SENHASEGURA’S BLOG
How to Create a Secure Password Policy?
Learn All About Passwordless Authentication
Password Strength: How to Create Strong Passwords for Credentials?
Version 2 Digital is one of the most dynamic IT companies in Asia. The company distributes a wide range of IT products across various areas including cyber security, cloud, data protection, end points, infrastructures, system monitoring, storage, networking, business productivity and communication products.
Through an extensive network of channels, point of sales, resellers, and partnership companies, Version 2 offers quality products and services which are highly acclaimed in the market. Its customers cover a wide spectrum which include Global 1000 enterprises, regional listed companies, different vertical industries, public utilities, Government, a vast number of successful SMEs, and consumers in various Asian cities.
About Segura®
Segura® strive to ensure the sovereignty of companies over actions and privileged information. To this end, we work against data theft through traceability of administrator actions on networks, servers, databases and a multitude of devices. In addition, we pursue compliance with auditing requirements and the most demanding standards, including PCI DSS, Sarbanes-Oxley, ISO 27001 and HIPAA.


![]()
One of the main goals of MITRE Engenuity’s ATT&CK® Evaluations is to help organizations better understand the level of visibility that endpoint detection and response (EDR) solutions offer to investigate in real time sophisticated threats lurking in a network. Visibility is a crucial metric in any organization’s assessment of an EDR solution it is considering to adopt or when learning the ropes of using one for the first time.
Obviously, visibility is not the only metric. The additional metrics considered in the ATT&CK Evaluations largely center around the context that accompanies the detection of specific adversarial techniques. These have a varying level of importance to each organization, depending on its level of maturity, the different regulations it needs to comply with, and a host of other sector-, company-, and site-specific needs. Yet there are other metrics, such as performance and resource requirements, alert fatigue, integration with other security software, and ease of use, that are unconsidered in the evaluations.
This rich palette of metrics in part reflects the success of EDR as a go-to tool for security defenders. Even organizations without dedicated security teams have gained interest in this type of defense tool. Yet the market is pushing EDR to become even better. Not infrequently, security defenders have been juggling between an EDR solution to hunt down threats and a security information and event management (SIEM) solution to sift through big data sets as complementary activities to defend their networks — the strategy being that what is lacking in one tool can be made up for by the other.
Some might think that if only a synthesis could be achieved between EDR and a security analytics platform, security defenders would have the ultimate tool in their hands. However, Forrester analysts see the situation differently. EDR needs to evolve into extended detection and response (XDR) by learning to ingest data feeds sourced beyond endpoints for analysis and response. Budding XDR solutions can then enter into a toe-to-toe competition with security analytics platforms in a race that appears destined for collision.
On the other side, to remain competitive, security analytics platforms need to be equipped with EDR features like higher-quality alerts and threat response capabilities and use resources more efficiently. The evolved solution that demonstrates better overall security is likely to become the increasingly favored tool for defenders. Our bet is that XDR has the winning odds because of its stronger foundation on EDR solutions that are designed for higher-quality detections with rich context, even if partially limited in overall visibility.
ESET adopts Forrester’s understanding of XDR as the next generation of EDR that moves beyond endpoints to collect data also from network devices, email servers, cloud-based services, and other sources and allows security defenders to discover and respond to more threats. In order to achieve this increased level of data collection and response capability, XDR can use two integration strategies: hybrid and native.
A hybrid strategy focuses on integrations with third-party tools. A native strategy focuses on integrations with tools from the same vendor. Currently, no vendor offers a complete XDR solution, making it an ideal yet to be achieved.
ESET is committed to building out a full XDR solution by iteratively improving ESET Inspect (formerly ESET Enterprise Inspector) and continuing to add integrations both with ESET’s ecosystem of security tools and with third-party tools. Previously, as ESET Enterprise Inspector, ESET’s EDR solution was positioned for enterprise security teams. Now, as ESET Inspect, it has evolved into the XDR-enabling component of the ESET PROTECT platform, ready for both large enterprise and smaller security teams.
Before looking at the ESET PROTECT platform, let’s consider ESET Inspect a little more closely.
More than being a mere name change, ESET Inspect is a new version with increased visibility and remediation capabilities. ESET Inspect carries over the familiar features of previous versions, such as the referencing to the MITRE ATT&CK knowledge base in its rule set, a REST API for integration with security orchestration, automation, and response (SOAR), SIEM, ticketing and other similar tools, and the ability to run a remote PowerShell session on Windows machines for precise response and remediation options.
In the latest version of the product — version 1.7 — several major Linux distributions are now supported. This adds to the already existing support for Windows and macOS and marks an important milestone on the road to a complete XDR solution. ESET Inspect’s coverage for Linux machines works in concert with ESET Endpoint Antivirus for Linux and ESET Server Security for Linux (from versions 9.0) to support the following distributions:
| Linux distributions supported by ESET Inspect | ||||
|---|---|---|---|---|
| Red Hat Enterprise Linux 7.6+ | Ubuntu LTS 18.04 | Debian 10 | SUSE Linux Enterprise 15 | Amazon Linux 2 |
| CentOS 7.6+ | Ubuntu LTS 20.04 | Debian 11 | Oracle Linux 8 | |
ESET Inspect also features an expanded rule set currently consisting of almost 1,000 rules. The rules are used to analyze events happening on endpoints, firewall and network data, user account actions, and other data for potentially malicious behaviors to be investigated by security engineers.
ESET researchers have enhanced a selection of rules with automated responses, for instance, to isolate a computer or block an executable. The use of an automated response in specific rules is made visible in the “Active Rule Actions” column of the “Detection rules” view:
The continued growth of ESET Inspect’s rule set and its integration with ESET’s other security products is a good example of building a native XDR solution. For ESET, the core of this integration lies in ESET PROTECT, a management console for IT admins to deploy and configure ESET security products. The ESET PROTECT platform packages endpoint security, server security, encryption, cloud-based, and detection and response solutions with the console to provide businesses a scalable prevention, detection, and response capability.
Thus, positioning ESET Inspect more closely to ESET PROTECT helps create a more integrated experience for security defenders using ESET’s security ecosystem. As mentioned above, one of the key goals of an XDR solution is to incorporate threat data beyond just endpoints, meaning that continuing to extend ESET Inspect’s coverage to more platforms and data sources that are already integrated with ESET PROTECT puts it firmly on the road to that goal.
ESET is building an XDR solution on the ESET PROTECT Enterprise platform, which packages ESET Inspect along with endpoint and server protection, cloud-based threat detection, and encryption to provide a comprehensive security capability.
XDR demands more data for ingestion, but this entails a need for greater database storage capacity that can hit performance hard if not adequately handled. Investing in more hardware to buttress on-premises database solutions is always possible, even if lacking some flexibility. This is why thinking ahead about the database needs for ESET PROTECT and the database needs for ESET Inspect is crucial.
With a cloud deployment, however, scaling up to meet this data storage demand is much more flexible as there is no need to buy new hardware. The cost lies rather in renting more storage space and possibly more powerful machines — a change that can be executed rapidly. The flexibility and scalability offered by the cloud are precisely the qualities required of an XDR solution, as Forrester points out.
Formerly, ESET PROTECT and ESET Inspect were only available for on-premises deployment, which could require considerable hardware investment, server maintenance costs, and on-site staff. While on-premises deployment remains an option, especially for organizations more desirous of keeping their data close to hand, both these solutions are also available in the cloud — a new capability for ESET Inspect since version 1.7 — and thus answer XDR’s call for cloud-native support.
In some cases, especially for smaller organizations or those whose core focus is outside of security, extracting value from an XDR solution can be too heavy of a lift to make unassisted. Similarly, managing ESET PROTECT Enterprise requires either full-time security staff or a managed detection and response (MDR) provider to take over some, if not all, of the daily security work.
For some time, the manufacturers and developers of complex products have recognized the need to increase the value of their products with a service offering. This is because at times customers struggled to see the value of their purchase when they did not have the expertise to use the product well, often misconfiguring it or failing to use all its features. More importantly, offering services reflects the type of relationship that providers wish to have with customers — for ESET that means engaging in a security partnership with customers.
ESET’s revamped MDR service assists security teams to set up ESET’s products with the best configuration and optimizations possible for their networks. The service also includes periodic health checks to address any poor security practices or misconfigurations that may have crept in over time. Critically, organizations can request the help of ESET security engineers for on-demand or proactive threat hunting with ESET Inspect.
Interested organizations (in select countries) can explore their options by reaching out via ESET’s MDR service web page.
This article started by discussing visibility and all the other metrics that organizations need to look at when considering a detection and response solution. For a snapshot of the depth of visibility that ESET Inspect can provide threat hunters, read the blogpost: Hunting down Sandworm and Wizard Spider: How ESET fared in the ATT&CK® Evaluations.
Designing a detection and response solution that balances all these metrics is by no means an easy task. The brief journey through XDR taken here has revealed a complexity of issues in developing native and hybrid integrations for EDR solutions and in scaling up data collection via cloud deployments, all while making detections of high quality and rich with context and maintaining high system performance.
While there are certainly mature organizations ready to wade through this complexity, the tough reality for most organizations is that they may have only one or two IT administrators … and they are managing security part time, along with their many other responsibilities. This can make the ATT&CK Evaluations, which concentrates on sophisticated threat groups, or even a discussion about XDR appear as somewhat of a niche focus.
However, both the evaluations and the pursuit of XDR speak to the gamut of security practices — from basic configurations and policies all the way to advanced fine-tuning and optimization — that should be in place to protect against even the most common threats. Furthermore, XDR’s demand for the cloud opens the door to improved security even for organizations without dedicated security teams. Such organizations may discover that their security practice falls short of industry standards when engaging in this discussion. At least in this way — by beginning the game of catch-up on their security — the ATT&CK Evaluations and the pursuit of XDR can provide actionable insight even to less mature organizations.
Version 2 Digital is one of the most dynamic IT companies in Asia. The company distributes a wide range of IT products across various areas including cyber security, cloud, data protection, end points, infrastructures, system monitoring, storage, networking, business productivity and communication products.
Through an extensive network of channels, point of sales, resellers, and partnership companies, Version 2 offers quality products and services which are highly acclaimed in the market. Its customers cover a wide spectrum which include Global 1000 enterprises, regional listed companies, different vertical industries, public utilities, Government, a vast number of successful SMEs, and consumers in various Asian cities.
About ESET
For 30 years, ESET® has been developing industry-leading IT security software and services for businesses and consumers worldwide. With solutions ranging from endpoint security to encryption and two-factor authentication, ESET’s high-performing, easy-to-use products give individuals and businesses the peace of mind to enjoy the full potential of their technology. ESET unobtrusively protects and monitors 24/7, updating defenses in real time to keep users safe and businesses running without interruption. Evolving threats require an evolving IT security company. Backed by R&D facilities worldwide, ESET became the first IT security company to earn 100 Virus Bulletin VB100 awards, identifying every single “in-the-wild” malware without interruption since 2003.



Everyday Loans is the UK’s leading independent loan lender, operating dozens of branches across the country and boasting a personal, hands-on approach to lending, uncommon in today’s digitally anonymous financial services industry.
Today, personal lending in the UK has grown to become an industry approaching 24 billion GBP, with recent acceleration due to widespread financial uncertainty and hardship in the wake of the COVID-19 pandemic.
The company’s IT department, led by Head of IT Tony Sheehan, experienced the tangible impact of this market growth as more and more customers walked through the doors of Everyday Loans’ many branches, and as the company increased its employee headcount in response to demand.
With more guests and customers on-site as well as a growing workforce, Sheehan and his team began to assess potential cybersecurity vulnerabilities – beginning with the corporate network.
Sheehan describes the company’s initial network security vulnerabilities: “We have a presence online, but we’re predominantly a face-to-face lender. We have over 75 offices with many new and repeat customers coming in to discuss a loan, as well as part-time staff for cleaning, security and maintenance. As a result, we knew network authentication was an obvious vulnerability.”
Implementing a solution for network authentication was a logical next step for Sheehan’s IT team. Given the increased branch foot traffic, the company needed to ensure it had total device awareness across the network. “This was a concern voiced to our new CTO when he came on board. He agreed, so we went about looking at different tools for network authentication and access control,” said Sheehan.
Another factor driving a focus on NAC was staff turnover. “Like every company, we have staff that leave us, and we need to ensure they can no longer access our network after they’ve departed,” said Sheehan. At that point in time, Everyday Loans knew that it’s usage of a hidden SSID paired with a PSK was not up to snuff from a security standpoint. As Sheehan and his team began to research potential solutions for network authentication and access control, two requirements became apparent:
Sheehan and his team found themselves at a crossroads as they mulled over these requirements. “We were either going to double down and stand-up another datacenter as part of a general infrastructure expansion initiative which would also enable us to deploy network access control on-premises, or we were going to go out and find a cloud-native NAC solution that fit our needs,” Sheehan said.
Portnox CLEAR was the only true cloud-native NAC we could find with the deployment and support model we wanted.
-Tony Sheehan, Head of IT at Everyday Loans
Having considered Microsoft NPS for RADIUS authentication and 802.1X, and Cisco ISE for full network access control, Sheehan and Everyday Loans’ IT team made the executive decision that neither tool was suited to their existing network security needs, internal skillsets, resource bandwidth or networking infrastructure. “We came across Portnox CLEAR fairly quickly thanks to the help of our partner, Haptic Networks,” Sheehan continued. “It was the only true cloud–native NAC we could find with the deployment and support model we wanted. Each of the other vendors had some solutions that were close in functionality, but in the end, they didn’t cover our needs totally – either functionally or operationally in terms of their ease-of-use. Ultimately, we went with Portnox CLEAR since it provided coverage across all our network devices and connected endpoints.”
After beginning a proof of concept of Portnox’s cloud-native NAC-as-a-Service, Everyday Loans ruled out competing alternatives. “It worked as expected. After comparing Portnox CLEAR’s robust, easy-to-use functionality to that of the other vendors up for consideration, we soon dismissed alternatives as they did not meet our technical security requirements,” Sheehan said.
The trial continued and Sheehan’s team threw every possible authentication and access control use case they could conjure up at the system to test its durability.
“Anyone with good network experience will pick up Portnox CLEAR with ease – it’s just a case of ensuring how you setup the network hardware and what control you have over employee and guest devices,” Sheehan went on to say.
Anyone with good network experience will pick up Portnox CLEAR with ease – it’s just a case of ensuring how you setup the network hardware and what control you have over employee and guest device.
-Tony Sheehan, Head of IT at Everyday Loans
Everyday Loans was able to deploy Portnox CLEAR across its 75 sites with relative ease, saving the company’s headquarters for last. “Portnox CLEAR has exceeded my expectations. Now that it is fully deployed, the visibility and control we have of users authenticating to the network is unparalleled,” Sheehan concluded.
“It is a huge bonus that the system easily integrates with Azure Active Directory and provides its own certificate authority out-of-the-box. Having multiple methods for authentications helps us ensure all our bases are covered. The solution has been reliable from day one.”
Version 2 Digital is one of the most dynamic IT companies in Asia. The company distributes a wide range of IT products across various areas including cyber security, cloud, data protection, end points, infrastructures, system monitoring, storage, networking, business productivity and communication products.
Through an extensive network of channels, point of sales, resellers, and partnership companies, Version 2 offers quality products and services which are highly acclaimed in the market. Its customers cover a wide spectrum which include Global 1000 enterprises, regional listed companies, different vertical industries, public utilities, Government, a vast number of successful SMEs, and consumers in various Asian cities.
About Portnox
Portnox provides simple-to-deploy, operate and maintain network access control, security and visibility solutions. Portnox software can be deployed on-premises, as a cloud-delivered service, or in hybrid mode. It is agentless and vendor-agnostic, allowing organizations to maximize their existing network and cybersecurity investments. Hundreds of enterprises around the world rely on Portnox for network visibility, cybersecurity policy enforcement and regulatory compliance. The company has been recognized for its innovations by Info Security Products Guide, Cyber Security Excellence Awards, IoT Innovator Awards, Computing Security Awards, Best of Interop ITX and Cyber Defense Magazine. Portnox has offices in the U.S., Europe and Asia. For information visit http://www.portnox.com, and follow us on Twitter and LinkedIn.。



Prometheus seeks to be a new generation within open source monitoring tools. A different approach with no legacies from the past.
For years, many monitoring tools have been linked to Nagios for its architecture and philosophy or directly for being a complete fork (CheckMk, Centreon, OpsView, Icinga, Naemon, Shinken, Vigilo NMS, NetXMS, OP5 and others).
Prometheus software, however, is true to the “Open” spirit: if you want to use it, you will have to put together several different parts.
Somehow, like Nagios, we can say that it is a kind of monitoring Ikea: you will be able to do many things with it, but you will need to put the pieces together yourself and devote a lot of time to it.
Prometheus, written in the go programming language, has an architecture based on the integration of third-party free technologies:

Unlike other well-known systems, which also have many plugins and parts to present maps, Prometheus needs third parties to, for example, display data (Grafana) or execute notifications (Pagerduty).
All those high-level elements can be replaced by other pieces, but Prometheus is part of an ecosystem, not a single tool. That’s why it has exporters and key pieces that in the background are other Opensource projects:
As we mentioned, Prometheus is an open-source monitoring tool.
The main difference with the rest of the tools we have, is that Prometheus is conceived as a framework for collecting data of undefined structure (key value), rather than as a monitoring tool. This allows you to define a syntax for your evaluation and thus store only in case of change events.
If you’re familiar with RRD, you’re thinking the right thing.
Prometheus does not store data in an SQL database.
Like Graphite, which does something similar, like other systems from another generation that store numerical series in RRD files, Prometheus stores each data series in a special file.
If you are looking for a Time series database information gathering tool, you should take a look at OpenTSBD, InfluxDB or Graphite.
Or rather, why NOT use Prometheus.
They themselves say it on their website: if you are going to use this tool to collect logs, DO NOT DO it, they propose ELK instead.
If you want to use Prometheus to monitor applications, servers or remote computers using SNMP, you may do so and generate beautiful graphics with Grafana, but first of all…
All Prometheus software configuration is done in YAML text files, with a rather complex syntax. In addition, each employed exporter has its own independent configuration file.
In the event of a configuration change, you will need to restart the service to make sure it takes the changes.
By default, Prometheus monitoring has no report type.
You will have to program them yourself using their API to retrieve data.
Of course, there are some independent projects to achieve this.
To have a dashboard in Prometheus, you’ll need to integrate it with Grafana.
There is documentation of how to do this, as Grafana and Prometheus coexist amicably.
If you need to process more data sources in Prometheus, you may always add more servers.
Each server processes its own workload, because each Prometheus server is independent and can work even if its peers fail.
Of course, you will have to “divide” the servers by functional areas to be able to differentiate them, e.g.: “service A, service B”. So that each server is independent.
There does not seem to be a way to “scale” as we understand it, since there is no way to synchronize, recover data and it does not have high availability or a common access framework to information on different independent servers.
But as we warned at the beginning, this is not a “closed” solution but a framework for designing your own final solution.
Of course, there is no doubt that Prometheus is able to absorb a lot of information, following another order of magnitude than other better known tools.
Somehow, each different “way” of obtaining information with this tool, needs a piece of software that they call “exporter”.
It is still a binary with its own YAML configuration file that must be managed independently (with its own daemon, configuration file, etc.).
It would be the equivalent of a “plugin” in Nagios.
So, for example, Prometheus has exporters for SNMP (snmp_exporter), log monitoring (grok_exporter), and so on.
Example of configuring an snmp exporter as a service:
To get information from a host, you may install a “node_exporter” that works as a conventional agent, similar to those of Nagios.
These “node_exporters” collect metrics of different types, in what they call “collectors”.
By default, Prometheus has activated dozens of these collectors. You may check them all by navigating to Annex 1: active collectors.
And, in addition, there are a multitude of “exporters” or plugins, to obtain information from different hardware and software systems.
Although the number of exporters is relevant (about 200), it does not reach the level of plugins available for Nagios (more than 2000).
Here we have included an example of an Oracle exporter.
Prometheus’ approach for modern monitoring is much more flexible than that of older tools. Thanks to its philosophy, you may integrate it into hybrid environments more easily.
However, you will miss reports, dashboards and a centralized configuration management system.
That is, an interface that allows observing and monitoring information grouped in services / hosts.
Because Prometheus is a data processing ecosystem, not a common IT monitoring system.
Its power in data processing is far superior, but the use of that data for day-to-day use makes it extremely complex to manage, as it requires many configuration files, many distributed external commands and everything must be maintained manually.
Here are the collectors that Prometheus has active by default:
These “node_exporter” collect metrics of different types, in what they call “collectors”, these are the serial collectors that are activated:
| arp | Exposes ARP statistics from /proc/net/arp. |
| bcache | Exposes bcache statistics from /sys/fs/bcache/. |
| bonding | Exposes the number of configured and active slaves of Linux bonding interfaces. |
| btrfs | Exposes btrfs statistics |
| boottime | Exposes system boot time derived from the kern.boottime sysctl. |
| conntrack | Shows conntrack statistics (does nothing if no /proc/sys/net/netfilter/ present). |
| cpu | Exposes CPU statistics |
| cpufreq | Exposes CPU frequency statistics |
| diskstats | Exposes disk I/O statistics. |
| dmi | Expose Desktop Management Interface (DMI) info from /sys/class/dmi/id/ |
| edac | Exposes error detection and correction statistics. |
| entropy | Exposes available entropy. |
| exec | Exposes execution statistics. |
| fibrechannel | Exposes fibre channel information and statistics from /sys/class/fc_host/. |
| filefd | Exposes file descriptor statistics from /proc/sys/fs/file-nr. |
| filesystem | Exposes filesystem statistics, such as disk space used. |
| hwmon | Expose hardware monitoring and sensor data from /sys/class/hwmon/. |
| infiniband | Exposes network statistics specific to InfiniBand and Intel OmniPath configurations. |
| ipvs | Exposes IPVS status from /proc/net/ip_vs and stats from /proc/net/ip_vs_stats. |
| loadavg | Exposes load average. |
| mdadm | Exposes statistics about devices in /proc/mdstat (does nothing if no /proc/mdstat present). |
| meminfo | Exposes memory statistics. |
| netclass | Exposes network interface info from /sys/class/net/ |
| netdev | Exposes network interface statistics such as bytes transferred. |
| netstat | Exposes network statistics from /proc/net/netstat. This is the same information as netstat -s. |
| nfs | Exposes NFS client statistics from /proc/net/rpc/nfs. This is the same information as nfsstat -c. |
| nfsd | Exposes NFS kernel server statistics from /proc/net/rpc/nfsd. This is the same information as nfsstat -s. |
| nvme | Exposes NVMe info from /sys/class/nvme/ |
| os | Expose OS release info from /etc/os-release or /usr/lib/os-release |
| powersupplyclass | Exposes Power Supply statistics from /sys/class/power_supply |
| pressure | Exposes pressure stall statistics from /proc/pressure/. |
| rapl | Exposes various statistics from /sys/class/powercap. |
| schedstat | Exposes task scheduler statistics from /proc/schedstat. |
| sockstat | Exposes various statistics from /proc/net/sockstat. |
| softnet | Exposes statistics from /proc/net/softnet_stat. |
| stat | Exposes various statistics from /proc/stat. This includes boot time, forks and interrupts. |
| tapestats | Exposes statistics from /sys/class/scsi_tape. |
| textfile | Exposes statistics read from local disk. The –collector.textfile.directory flag must be set. |
| thermal | Exposes thermal statistics like pmset -g therm. |
| thermal_zone | Exposes thermal zone & cooling device statistics from /sys/class/thermal. |
| time | Exposes the current system time. |
| timex | Exposes selected adjtimex(2) system call stats. |
| udp_queues | Exposes UDP total lengths of the rx_queue and tx_queue from /proc/net/udp and /proc/net/udp6. |
| uname | Exposes system information as provided by the uname system call. |
| vmstat | Exposes statistics from /proc/vmstat. |
| xfs | Exposes XFS runtime statistics. |
| zfs | Exposes ZFS performance statistics. |
This is an example of the type of information that an Oracle exporter returns, which is invoked by configuring a file and a set of environment variables that define credentials and SID:
To get an idea of how an exporter is configured, let’s look at an example, with an JMX exporter configuration file:
---
startDelaySeconds: 0
hostPort: 127.0.0.1:1234
username:
password:
jmxUrl: service:jmx:rmi:///jndi/rmi://127.0.0.1:1234/jmxrmi
ssl: false
lowercaseOutputName: false
lowercaseOutputLabelNames: false
whitelistObjectNames: ["org.apache.cassandra.metrics:*"]
blacklistObjectNames: ["org.apache.cassandra.metrics:type=ColumnFamily,*"]
rules:
- pattern: 'org.apache.cassandra.metrics<type=(\w+), name=(\w+)><>Value: (\d+)'
name: cassandra_$1_$2
value: $3
valueFactor: 0.001
labels: {}
help: "Cassandra metric $1 $2"
cache: false
type: GAUGE
attrNameSnakeCase: false Version 2 Digital is one of the most dynamic IT companies in Asia. The company distributes a wide range of IT products across various areas including cyber security, cloud, data protection, end points, infrastructures, system monitoring, storage, networking, business productivity and communication products.
Through an extensive network of channels, point of sales, resellers, and partnership companies, Version 2 offers quality products and services which are highly acclaimed in the market. Its customers cover a wide spectrum which include Global 1000 enterprises, regional listed companies, different vertical industries, public utilities, Government, a vast number of successful SMEs, and consumers in various Asian cities.
About PandoraFMS
Pandora FMS is a flexible monitoring system, capable of monitoring devices, infrastructures, applications, services and business processes.
Of course, one of the things that Pandora FMS can control is the hard disks of your computers.
Need help? Our team is just a message away