FAQs
What is Monitoring Service?
The Monitoring Service offers a centralized and scalable solution for monitoring and analyzing your application and infrastructure metrics. It enables you to track performance, detect issues proactively, and ensure optimal operation across your systems.
What types of metrics can be monitored?
The Monitoring Service supports a wide range of metrics, including system performance, application performance, network traffic, and custom metrics specific to your applications. Metrics must be Prometheus-compatible.
How frequently are metrics pushed to the server?
Metrics are pushed to our servers at configurable intervals to match your monitoring needs. The default push interval is one minute. You can adjust this interval based on your requirements.
Can I set up custom alerts for specific metrics?
Yes, you can easily configure custom alerts directly within Grafana for specific metrics. The Monitoring Service utilized Grafana for visualization, allowing you to define alert conditions, thresholds, and notification preferences.
How secure is the data collected by the Monitoring Service?
The Monitoring Service employs multiple layers of security to ensure data protection:
Transport Layer Security (TLS): Data is encrypted during transmission.
Data Partitioning: Each user's data is stored in separate partitions to ensure isolation.
Encryption: Both server-side and client-side encryption are used to secure data at rest.
Can I customize the dashboards in the Monitoring Service?
Yes, Monitoring Service offers powerful dashboard customization capabilities through Grafana. Create, modify, and share interactive dashboards to visualize your data in the way that best suits your needs. Grafana's rich feature set allows you to build highly informative and engaging dashboards.
How do I manage user access to the Monitoring Service?
User access is managed through a robust role-based access control Role-Based Access Control (RBAC) system. Administrators can create user accounts, assign roles, and define permissions to control access to different features and data within the Monitoring Service.
What is the difference between Monitoring as a Service and Monitoring Service?
Feature | Monitoring as a Service (MaaS) | Monitoring Service |
Management Level | Fully managed; no agent management required | User-managed; users configure and manage their own agents |
Metric Collection Mechanism | Abstracted; automatic for IONOS Cloud VMs | Push-based; users push metrics to provided endpoints |
Deployment | Restricted to IONOS Cloud VMs | Flexible; supports Cloud-agnostic and On-Premise environments |
Metric Scope | Limited to CPU, network, and storage metrics | Extensive; includes host-based, application, network, system metrics, etc. |
Customization | Limited; out-of-the-box solution | Highly customizable; compatible with Prometheus-compatible metrics |
Data Retention | Basic; limited retention period | Extensive; flexible retention options based on configuration |
Cost | Free | Billed per 1 million samples |
Note: From September 1, 2024, Monitoring as a Service will receive limited support and updates. For enhanced features, greater flexibility, and future-proof monitoring capabilities, we recommend using Monitoring Service.
Can I restrict the traffic sent to Monitoring Service endpoints?
Yes, we recommend configuring firewall rules using the authorized IP addresses associated with each endpoint to restrict the traffic to Monitoring Service endpoints. The following is a list of locations and their specific IP addresses:
| Location | Region-specific Endpoints | IP addresses |
|---|---|---|
Berlin |
|
|
Logroño |
|
|
London |
|
|
Frankfurt |
|
|
Paris |
|
|
What is Cloud Native Computing Foundation?
The Cloud Native Computing Foundation (CNCF) is part of the Linux Foundation, focused on advancing cloud-native technologies. It hosts projects like Kubernetes and Prometheus, provides certification, and promotes standards for cloud-native computing.
For more details, visit the CNCF website.
Last updated