PingView — External Uptime Monitoring
| 开发者 | marcinatpingview |
|---|---|
| 更新时间 | 2026年8月5日 05:26 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
- Current status, uptime for the last 24 hours and 7 days, and response time
- A 24 hour availability chart, one block per time bucket, so a short outage is visible instead of averaged away
- Per-location results, so you can tell "the site is down" apart from "the site is slow from one region"
- SSL certificate and domain registration expiry, with days remaining
- A quality report with the daily Lighthouse scores for performance, accessibility, best practices and SEO, and the Core Web Vitals behind them: LCP, CLS and TBT
- A security header grade from Mozilla HTTP Observatory, with the score out of 100, so a missing Content-Security-Policy or HSTS header shows up before an audit finds it
- Recent incidents: what broke, when, and how long it lasted
- A status indicator in the admin bar on every screen
- Checks your site from external locations on the interval in your plan
- Sends downtime alerts to email, Slack, Microsoft Teams, Discord, webhooks, or SMS
- Warns before an SSL certificate or domain registration expires
- Runs daily Google Lighthouse scans for performance and Core Web Vitals, plus a Mozilla HTTP Observatory scan of your security headers, on paid plans
- Publishes a status page you can share with clients
- Install and activate the plugin
- Enter the address alerts should go to
- PingView creates an external monitor and starts checking your site
安装:
- Upload the plugin files to
/wp-content/plugins/pingview-external-uptime-monitoring - Activate the plugin through the 'Plugins' screen in WordPress
- Navigate to PingView in the admin menu
- Enter your email and click "Start Monitoring"
- Review the newly created monitor in PingView
屏幕截图:
常见问题:
Do I need a PingView account?
No! The plugin automatically creates a monitoring account for you during setup.
How often is my site checked?
The check interval and locations depend on the monitor configuration and the PingView plan connected to the plugin.
What happens when PingView detects an outage?
PingView sends an email alert according to the monitor and notification settings. The plugin dashboard also shows the current status.
Does it monitor Core Web Vitals?
Yes, on paid plans. PingView runs a daily Google Lighthouse scan from outside your hosting and shows the performance, accessibility, best practices and SEO scores in your WordPress admin, together with the lab Core Web Vitals behind the performance score: LCP, CLS and TBT. It is a monitor, not an optimizer, so it reports where you stand and when a deploy makes it worse. It does not cache, minify or defer anything on your site.
Does it check my security headers?
Yes, on paid plans. PingView runs a Mozilla HTTP Observatory scan and shows the grade (A+ to F) and score out of 100 next to your SSL and domain checks, so a missing Content-Security-Policy, HSTS or X-Frame-Options header is visible from the dashboard. This is an external check of what your site sends over HTTP; it is not a firewall or a malware scanner and does not replace one.
Does this affect my site performance?
No. Monitoring checks come from external servers and don't impact your site's performance.
How is this different from a plugin that monitors from inside WordPress?
A plugin running on your server can only report while your server is up. If PHP crashes, the host goes down, or DNS breaks, an internal check goes silent instead of alerting you. PingView checks from outside, so those are exactly the cases it catches.
Is it free?
Yes, the plugin and the monitoring it sets up are free to start. Paid plans add shorter check intervals, more locations, more alert channels, Lighthouse and security scans, and public status pages.
Where can alerts be sent?
Email works out of the box. Slack, Microsoft Teams, Discord, webhooks and SMS are configured in your PingView account and apply to this monitor too.
Can I show my customers a status page?
Yes. PingView publishes a status page for your monitors that you can share with clients or link from your site.
I already use PingView. Can I connect an existing account?
Yes. On the setup screen choose "Connect with an API key" and paste the key from your PingView dashboard.
What happens after disconnecting or uninstalling the plugin?
The plugin removes its local connection data when you disconnect, and removes all local plugin data when you uninstall it. The remote PingView monitor and account remain active. Sign in at https://pingview.app to pause or delete the monitor and manage the account.
更新日志:
- Added: Security headers now have their own card. It shows the Mozilla HTTP Observatory grade and score, the checks your site fails, what each one protects against, and how many points fixing it wins back.
- Added: A copy button next to every failed check, with the exact header line to paste into your server configuration.
- Improved: The failed checks are ordered by how much they are worth, so the fix with the biggest effect is first. Smaller ones stay collapsed.
- Improved: The alerts card now points at the weekly summary, for the weeks when nothing breaks.
- Fixed: The speed score changed on every refresh even when nothing about the site had. It restated the response time shown next to it and could not be acted on, so it is replaced by "Needs attention", which counts the certificate, domain and uptime issues waiting for you.
- Added: A status indicator in the admin bar, so you can see whether the site is up without opening the PingView screen.
- Added: A link to PingView on the Plugins screen, and the setup screen now opens right after activation.
- Fixed: The location list only showed locations that had already reported, so a monitor covering several locations could claim it was checked from one, or show no locations at all until the first results arrived.
- Fixed: Cancelling the "Connect with an API key" form left the key sitting in the field.
- Improved: Status and error messages are now announced by screen readers, and the API key form reports whether it is open.
- Added: A quality report card with the daily Google Lighthouse scores for performance, accessibility, best practices and SEO, plus Core Web Vitals.
- Added: The Mozilla Observatory security grade for your site, next to the SSL and domain checks.
- Added: An overview of where alerts are delivered, covering email, Slack, Microsoft Teams, Discord, webhooks and SMS.
- Fixed: The performance score changed on every refresh, because it was based on a single check. It is now based on the 95th percentile response time over 24 hours and is labelled "Speed score, 24h".
- Added: The status screen now lists every monitoring location your plan checks from, with its own status and response time.
- Added: A 24 hour availability chart, one block per time bucket, so a short outage is visible at a glance instead of hidden in an average.
- Added: A recent incidents list showing what broke, when, and how long it lasted.
- Fixed: The "Where should we send alerts?" text on the setup screen was not a real form label, so clicking it did not focus the field and screen readers did not announce it.
- Fixed: The refresh button icon sat off the text baseline.
- Fixed: Refreshing only cleared part of the cached data, so some panels could keep showing older values.
- Improved: Rebuilt the setup screen around a single card, so the connection form is no longer competing with a marketing panel for attention.
- Improved: The panel is centred and uses more of the available width on wide screens.
- Improved: The status screen now shows which version of the plugin is installed.
- Fixed: The incident banner never appeared, because open incidents were read from a field that does not exist. Active incidents are now shown with their reason and start time.
- Fixed: The performance score changed on every refresh even when the underlying data had not. The same response time now always produces the same score.
- Fixed: Sites monitored over plain HTTP no longer sit on "Checking certificate..." forever. They now state that no certificate applies.
- Fixed: A domain without registration data no longer shows an endless "Checking domain registration...".
- Fixed: The refresh button was rendered several times with the same HTML id, so only the first one worked.
- Improved: Redesigned the status panel around a header card, a four-tile metric strip, and a two-column layout.
- Improved: Response times, uptime percentages, and scores are set in a monospaced face so values line up and stay comparable.
- Improved: Every status is now conveyed by colour, icon, and text label together, never colour alone.
- Improved: The setup screen no longer promises a first check "in ~5 minutes" when the backend has not scheduled one yet.
- Improved: Honoured reduced-motion preferences and tightened the layout on small screens.
- Fixed: Prevent an undefined SSL expiration warning when certificate data is incomplete.
- Improved: Redesign the monitoring dashboard for clearer desktop and mobile layouts.
- Improved: Remove horizontal overflow and improve visual consistency.
- Security: Escape all API messages rendered in the admin dashboard.
- Security: Store new API tokens using authenticated encryption and fail safely when encryption is unavailable.
- Fixed: Render canonical PingView monitor statuses without reducing them to UP or DOWN (BR-STATUS-01 / CT-STATUS).
- Improved: Require an explicit, unchecked consent before sending setup data to PingView.
- Improved: Align feature descriptions with plan-dependent intervals and locations.
- Fixed: Load all admin CSS through the WordPress enqueue API.
- Fixed: Match the translation text domain to the WordPress.org plugin slug.
- Improved: Fully document the PingView external service and transmitted data.
- Tested: WordPress 7.0 with WP_DEBUG enabled.
- Fixed: Plugin URI updated to working URL
- Improved: Documentation for external service usage
- Updated: Contributors metadata
- Initial release