GLWS · Monitoring
Collect time-series metrics and query the behaviour of your infrastructure and applications.
Common uses of Prometheus.
Memory and storage needs depend on active series, scrape intervals and retention. Keep metric labels bounded and restrict access to the query interface.
Planning examples, not official minimum requirements.
Monitoring
Check the current supported operating systems, deployment methods, dependencies and licence terms. What you need depends on your workload, not just the application's name.
Large datasets and busy workloads can need far more memory, storage or different hardware. Any external API or service subscriptions are separate.
Read the Prometheus documentation ↗ (opens in a new tab)Advice specific to this application.
Count monitored targets and the metrics each exposes. Labels that contain arbitrary user IDs or request values can create many time series. Select scrape intervals and retention that fit the questions you want to answer, then watch actual memory and storage growth.
Metric collection, rule evaluation and sending notifications are separate steps. Decide whether Alertmanager or another service will handle delivery, and test the full path. Keep the scrape configuration and alert rules under version control and restrict administrative endpoints.
Linux guides that help with this setup.
Read the basic resource indicators on Ubuntu 24.04 LTS and AlmaLinux 9, then identify where to investigate a slowdown.
Read guide →Allow the SSH port you actually use before enabling UFW or firewalld, then test access from another terminal.
Read guide →Understand status, start, enable, reload, and restart so you can manage services without unnecessary interruptions.
Read guide →Four steps that make the environment easier to maintain.
Read the publisher's instructions and choose a supported installation method.
Protect the dashboard, credentials and network endpoints before you expose any service.
Work out where the application keeps its state and store it separately from replaceable runtime files.
Back up the data and configuration, then check that you can restore them.
Run through it before and after you install.
$ application-checklist --name prometheus
[ ] Supported deployment method
[ ] Authentication and access restrictions
[ ] Independent data backup
[ ] Updates and restoration tested
root@glws:~#
Quick answers before you choose resources.
No. The configurator only saves your application preference. It does not connect to any infrastructure or run an installer.
Use the planning example as a starting point only. Check the publisher's requirements and measure the whole stack under a realistic workload.
You do. Self-hosted applications need updates, configuration and recovery planning from the operator. The publisher's documentation describes supported maintenance.
The knowledge base covers Linux access, packages, services, firewalls and backups.
Other tools you might run alongside or instead.
Check service availability and organise notifications through a self-hosted monitoring dashboard.
Explore application →Turn metrics and logs from connected data sources into dashboards for your services.
Explore application →Website, email, DNS and database management in a hosting dashboard.
Explore application →A self-hosted assistant for connecting model-powered tasks with tools and messaging.
Explore application →