A crowded market…
In the observability market, fierce competition is taking place with the emergence of tools based on open-source projects as well as commercial solutions. Large commercial providers are trying to solidify their dominance in the market by providing not only metric monitoring solutions, but also monitoring services such as log, security, database, APM services, and AI/ML ops. To compete with these large commercial solution providers, several startups are aiming to differentiate themselves through creative ideas regarding monitoring dashboards and application tracing. Additionally, open source-based service providers are launching managed services that overcome the limitations of OSS projects, including Prometheus’ long-term storage concerns. Examples include the enhanced trace capability offered by Honeycomb.io‘s “BubbleUp” function, the integration of market-leading dashboards such as Kibana and Grafana by Logz.io, as well as the M3-based long-term storage function provided by Chronosphere.
As cloud-native services enter the majority stage commercially, the observability market is also fiercely competitive. So you may wonder – why does NexClipper want to enter this market?
Still many challenges
Observability doesn’t just happen, it requires a lot of resource and maintenance. First, you need to have a solution that monitors the observability target and further, the solution needs to be maintained upon any change of the targets.
The increase in monitoring targets makes observability more challenging. Even if alert rules are changed, efforts to reflect them may require significant resources and cause business risks due to errors until a separate automation tool is implemented. Additionally, if the monitoring target is not a Kubernetes-based service but diversified such as BareMetal and IOT devices, operation difficulty further increases.
The objective of observability is not monitoring alone, but to identify the cause of an incident and apply a solution to solve it. While solutions have continuously added new monitoring methods in the past, in an attempt to provide more and more information to users, in this flood of dashboards and alarms it is still difficult to find the root cause of a problem. In order to solve this problem, more advanced APM solutions and improvement plans such as applying AI/ML to find the cause of failure are emerging, and improvement and innovation in this field will continue.
Innovative new services for cloud-native technology are constantly appearing, and companies actively using such services are ever increasing. As these new services are used commercially, there is also a demand for observability for them. Therefore, how quickly observability for a new service can be provided with a verified solution is also becoming an important measure regarding observability. On one hand, in the case of many commercial observability providers, it takes time to secure the observability of new services. On the other hand, for open source-based services, you can easily find metric exporters developed by the community for example through Github, but it is difficult to know how reliable these exporters are until you try and verify them yourself.
Why observability with NexClipper?
NexClipper is an observability service based on OSS projects such as Prometheus, Loki, Tempo, and Grafana. By automating various tasks from installation to operation, customers can easily utilize the service on private and public clouds, as well as bare-metals. In addition, metric, log, and trace are integrated to help identify the cause of the incident. Look out for our upcoming articles introducing the features in details soon! Today, learn all about how NexClipper sets out to overcome many of the addressed challenges.
1. Distributed cloud resource management
NexClipper focuses on the management of resources in a distributed cloud environment. Automating and standardizing resource management is essential, not only for securing observability but also other DevOps operations.
Klevr, an OSS project of NexClipper, uses a dispatched agent regardless of the type of target computing resource, in order to asynchronously take and execute the service catalog instructed by NexClipper’s Klevr Server and to report the execution result. A service catalog is a standardized template for provisioning by Helm chart, operation execution by shell script, and so on. This template can be applied directly to the computing zone or can be scheduled, enabling efficient and effective operations regardless of the type or number of computing resources. In other words, you can think of it as a service that dispatches workers to distributed data centers, provides standardized manuals, executes them at scheduled times, and reports execution results. For further technical details, you can learn more about Klevr and Provbee on our Open Source page. Additionally, they will be introduced in depth in one of our upcoming articles.
2. Intelligent metric operation
NexClipper’s Alert Hub enables metric-based intelligent operations: It helps users to manage who and what channels should receive alerts and notifications. Resources on a per-cluster and per-service basis can be assigned to groups of users to support alerts and analytics only for those resources that are needed. Additionally, alerts and notifications issued by Prometheus and DevOps operations, related metrics, as well as countermeasures are integrated through incidents to facilitate the resolution. This history will serve to solve incidents that may occur in the future. The accumulated information will be the basis of AI/ML-based operations, which will be added to NexClipper in the future**.** NexClipper will provide an automation service (development environment installation, deployment) for DevOps operations in the future and this history will be a key input for Intelligent metric operation.
3. Unlimited supply of service monitoring
NexClipper ExporterHub is an OSS that provides alert configuration and Grafana dashboard design using verified exporters among exporters on Github. NexClipper supports the automatic installation of the corresponding exporters so that users can implement it easily. Users can test the exporter on Github, understand the meaning of the metric, install the exporter, reduce the burden of creating alerts and dashboards, and use the monitoring service immediately.
NexClipper plans to upgrade the functions of the current ExporterHub version and provide documentation on detailed functions of each registered exporter in order to support the easy use of various exporters.
See you @ KubeCon + CloudNativeCon North America October 2021 in LA
NexClipper is currently conducting closed beta testing and is planning to launch an open global beta version soon, in time for KubeCon + CloudNativeCon North America. We are also looking forward to meeting you during the exhibition days from October 11 to 15 – either in person at booth SU13 or by visiting our virtual booth.
Join us in LA while we prepare for our first voyage into the open cloud-native sea. We will support free use of NexClipper unit the end of the year and welcome your feedback!
If you would like to discuss more about this topic, please contact firstname.lastname@example.org.