Uptrends
Website, API and server monitoring with synthetic and real user performance checks
Synthetic monitoring built for people who script their checks, not click them.
◆Recent moves
- 15d ago
Windows Server 2022 is now the minimum for new private location installations
The Windows Server 2019 installer is withdrawn for new private locations, making Server 2022 the minimum, while existing 2019 installations stay supported with updated container images. A support-matrix change that affects only new deployments.
View source ↗ - 1mo ago
Monitor API behavior every 30 seconds
New Enterprise accounts can run multi-step API monitors every 30 seconds instead of every minute, halving worst-case detection time on the checks customers care most about. Gated to a tier, which is where the sharper capabilities in this feed tend to land.
View source ↗ - 1mo ago
Authenticate multi-step APIs with bearer tokens
Multi-step API monitors can authenticate individual calls with a bearer token, which Uptrends then attaches to each request's Authorization header. One of the pieces that lets a synthetic check exercise an authenticated API rather than only its public edge.
View source ↗ - 1mo ago
Duplicate custom integrations to create new ones faster
Custom integrations can be saved as copies, so a working configuration can be reused rather than rebuilt. It does not extend to built-in or third-party integrations with their own setup flows, which limits it to the teams already maintaining several hand-rolled ones.
View source ↗ - 2mo ago
Introducing Uptrends OpenTelemetry export
Monitoring results from selected monitor groups can be exported to an OpenTelemetry collector, putting digital experience data next to application, infrastructure and log telemetry in Elastic, New Relic, Splunk or Prometheus. It requires contacting support to enable, so it is a supported capability rather than a self-serve one.
View source ↗ - 2mo ago
Introducing JSON Web Token (JWT) user-defined functions
JWT encode and decode become user-defined functions in multi-step API monitors, letting a check sign its own token with a key and read claims back out. Together with bearer authentication it removes the main reason these monitors previously needed an external step.
View source ↗