Core Design Principles Behind Uplinkr

Uplinkr is intentionally minimal.

This is not a missing feature list.
It is a set of conscious design decisions made to keep monitoring reliable, portable and free of unnecessary dependencies.

Philosophy: “Is the light on?”

Uplinkr answers a very simple question:

Is the system reachable – yes or no?

It does not try to be a full monitoring suite. It does not try to visualize everything. It focuses on one thing: detecting when something is wrong and alerting you.

Sometimes you don’t need a dashboard.
You just want to know whether the light is on.

Why there is no dashboard

Uplinkr deliberately ships without a dashboard.

Dashboards introduce:

persistent storage requirements
UI maintenance
authentication concerns
operational overhead

All of that moves the focus away from the core problem.

uplinkr is built to be:

CLI-first
scheduler-friendly
automation-ready

If you need a dashboard, uplinkr can feed data into your existing tools. It does not force you into yet another UI.

Why file-based instead of database-first

uplinkr does not require a database.

This is intentional.

Benefits of a file-based approach:

no schema migrations
no database coupling
works in minimal environments
easy to inspect, archive or parse
ideal for cron-based setups

A database can be added later. A database requirement cannot easily be removed.

Why uplinkr does not replace monitoring platforms

uplinkr is not a replacement for large monitoring platforms.

It is designed for situations where:

you want local control
you don’t want to depend on an external monitoring provider
you need a lightweight check inside existing infrastructure
you prefer simple automation over complex setups

uplinkr can coexist with other tools. It does not compete with them.

Integration with existing tools

uplinkr is designed to work alongside your existing infrastructure:

Log-based workflows:

Export alerts to centralized logging (ELK, Splunk, Datadog)
Use your existing log-based alerting rules

Webhook integrations:

Forward alerts to Slack, Discord, or Teams
Trigger PagerDuty or Opsgenie incidents
Feed data into custom dashboards or APIs

File-based analysis:

Parse JSON probe results with your own scripts
Archive data to S3 or other cloud storage
Build custom reports from probe history

See Alerting & Notification Channels for practical examples.

Opinionated, but extendable

uplinkr makes a few strong assumptions:

alerts matter more than visuals
reliability beats feature richness
simplicity scales better than complexity

At the same time, the architecture is designed to be extendable. More features can be added without breaking the core philosophy.