Targets and exporters
Connect systems, applications and devices with explicit labels.

We install, integrate and operate Prometheus as a monitoring platform - including exporters, service discovery, PromQL, Alertmanager, retention and scaling.
Companies worldwide trust WZ-IT
The following are trademarks of their respective owners: Prometheus (The Linux Foundation and the Prometheus Authors). WZ-IT is an independent service provider and has no business, partnership, or contractual relationship with these companies. We offer independent migration, installation, hosting, and operations services.

Prometheus collects metrics using a pull model and makes them queryable with PromQL. Production monitoring still requires clean labels, suitable exporters, documented rules and alert paths without unnecessary noise.
We design targets, service discovery, recording rules, Alertmanager, dashboards and retention. WZ-IT can respond to alerts or pass them to your team according to the agreed service level.
Prometheus detects technical states. Business-critical thresholds, recipients and expected responses must be agreed for each platform.
Long-term retention, global queries and highly available designs may require additional components such as remote-write targets or a federated monitoring layer.
Targets, rules, alert paths and storage are maintained, tested and monitored like production code.
Connect systems, applications and devices with explicit labels.
Structure time series, rules and queries in a controlled way.
Define priorities, routing, silences and escalation.
Own updates, storage, backups and self-monitoring.
WZ-IT operates the monitoring platform and can respond to alerts; business thresholds and owners are defined together.
| Area | Responsibility | Scope and boundaries |
|---|---|---|
| Prometheus and Alertmanager | WZ-IT | Installation, configuration, updates, monitoring and backup. |
| Exporters and service discovery | WZ-IT | Connect agreed targets and monitor their reachability. |
| Alert rules | Shared | WZ-IT writes technical rules; the customer confirms impact and priority. |
| Incident response | Shared | Response follows the booked service level and documented runbooks. |
| Application metrics | Customer | Instrumentation and business meaning come from the development team. |
| Long-term storage and HA | Optional WZ-IT service | Remote write, Thanos/Mimir-style designs or federation are planned separately. |
Connect exporters and instrumented applications through controlled scrape targets.
Discover dynamic systems across cloud, Kubernetes and private environments.
Maintain queries, recording rules and technical indicators as versioned configuration.
Group, route and silence alerts and deliver them to defined on-call channels.
Provide dashboards with clear sources, ownership and drill-down paths.
Size cardinality, local storage and remote write around metric volume.
Assess existing data and configuration, migrate them in a test run and move to managed operations through a controlled cutover.
Secure SSO, roles, administrative paths and external access for the application and existing infrastructure.
Back up all stateful components consistently and document the recovery path for the agreed scope.
Monitor and update the application and its technical dependencies and operate them under the agreed service level.
A clearly defined operating scope instead of an opaque hosting flat fee.
We set up a test instance for you, usually on the next business day. No payment details required. After seven days it is deleted unless you continue.
We combine the right compute size with ongoing operations, backups, monitoring and a service level appropriate for the criticality of Prometheus. High availability and recovery targets are designed separately where needed.
We also design custom hosting architectures, integrations and migrations around Prometheus. Contact us for a technical assessment.
One managed standard Prometheus application is included in the Starter workload. Business and higher levels add a flexible operations allowance for planned work during regular service hours. Select compute, additional applications, storage and the appropriate service level.
A workload is one compute instance with the applications agreed for it.
One standard app per workload is already included. Additional dedicated servers count as separate workloads.
€79.90 per started TB and month, including daily encrypted offsite backup with 7-day retention.
Enquiry
Briefly describe the current state and objective for Prometheus. We assess infrastructure, integration, and ongoing operations.
Active series, scrape interval, label cardinality, rule count and retention determine storage, memory and CPU.
| Usage scenario | Technical starting point | Key factors |
|---|---|---|
| Small server estate | One Prometheus + Alertmanager | A manageable target set and local retention. |
| Multiple platforms or teams | Separate Prometheus instances | Failure domains and ownership are separated. |
| High cardinality | Metrics assessment | Series growth, labels and scrape frequency are measured. |
| Long-term data or global view | Platform assessment | Remote write, object storage, query layer and HA are evaluated. |
The calculator covers a manageable standard Prometheus instance. Many targets, high cardinality, long retention, additional dashboards and the required incident response are added after technical discovery.
Monitoring should be independent enough to detect and report failures of its target platform.
Dedicated instance with defined private access to your targets.
Metric collection inside your cloud networks and accounts.
Monitoring for local servers, networks, equipment and applications.
Separate collector layers for cloud, sites and central alerting.
Prometheus collects metrics from defined targets; Alertmanager sends relevant signals into a documented response process.
Dashboards, queries, alerts, runbooks and incident communication.
TLS, private networks and restricted administrative endpoints.
SSO at the frontend plus controlled recipients and integrations.
Scraping, rules, time series, grouping and routing.
Servers, applications, Kubernetes, databases and network devices.
Local time series or separate long-term storage.
Grafana, email, chat, ticketing and on-call systems.
The monitoring platform monitors itself: missing scrapes, rule failures, storage limits and undelivered alerts are treated as operating risks in their own right.
Answers about exporters, alerting, Grafana, retention and takeovers.
Yes, when incident response is included in the agreed service level. Alternatively, we operate the platform and forward alerts to your team.
Grafana can be integrated for visualisation. Dashboards, user access and operations are defined in the scope.
Yes. We review syntax, labels, dependencies, alert noise, delivery channels and missing runbooks and prioritise remediation.
Local retention is configurable but limited by series volume and storage. For long retention or global queries, we assess remote-write and object-storage designs.
Yes, when applications expose suitable metrics. WZ-IT connects endpoints and rules; business instrumentation can be implemented with your development team.
As an alternative to managed hosting in the data centre, WZ-IT provides the hardware, configures Prometheus, and handles hardening, monitoring, updates, backup and technical support. Access can be limited to the internal network or enabled through VPN and existing identities.
from EUR 349 excl. VAT / month · plus one-time provisioning and initial setup

These solutions are often used together with Prometheus
These solutions offer similar functionalities and can be evaluated together
No risk: worst case, you leave with a clearer understanding of your project than before.


“WZ-IT's advice on our Azure migration was technically sound and completely non-binding right from the intro call - we took away a great deal.”
Whether a specific IT challenge or just an idea - we look forward to the exchange. In a brief conversation, we'll evaluate together if and how your project fits with WZ-IT.