SleekView Charts for EasyCron
SleekView Charts reads the access log that EasyCron's hits leave on your install, plus a small request-id table, and renders call counts, status codes, response time and per-endpoint failure rate as Number, Pie, Bar and Area cards.
♾️ Lifetime License available
External cron without a dashboard is a black box
EasyCron solves the most fragile part of WordPress: wp-cron's reliance on real visitors to trigger scheduled work. It calls a URL on your site on a precise schedule from outside infrastructure. Brilliant when it works, opaque when it does not. The EasyCron dashboard lives in their UI, on their domain, scoped to their account. The WordPress side sees only the hits.
SleekView Charts closes that loop. A small mu-plugin tags each EasyCron request (either by matching the EasyCron user agent or by reading a shared secret in the query) and writes a row with the endpoint, HTTP status returned, response time and timestamp. With that table in place, an EasyCron call becomes a first-class data point on the WordPress side. A Number card counts pings in the last 24 hours. A Pie splits 2xx, 4xx and 5xx. A Bar groups by endpoint so a failing job is its own row. An Area trends response time so a slow checkout cron is visible weeks before it times out.
The external service stays where it is. SleekView just gives the receiving side a measurable surface so failures are caught on the WordPress install instead of waiting for an EasyCron email or a missing daily report.
Workflow
Turn EasyCron hits into a dashboard
Tag the incoming requests
Point SleekView at the table
Compose the chart cards
Save and gate
Sample dashboard
Charts you can build from EasyCron data
Pings, last 24h
Count
Status code split
Count
group by status
Calls per endpoint
Count
group by endpoint
Average response time per hour
Average(duration_ms)
group by hit_at
Comparison
Default EasyCron logs vs SleekView Charts
Default EasyCron logs
- Logs live in the EasyCron dashboard, scoped to one account
- No visibility on the WordPress side of how each call actually performed
- Failures only surface via email alerts or by manually opening the EasyCron UI
- No long-term response time trend, so slow degradation is invisible
- Per-endpoint comparisons need a spreadsheet or screen scraping
SleekView Charts
- KPI card for total external pings in any window
- Pie split of 2xx, 4xx and 5xx as seen from the WordPress side
- Bar of calls per endpoint to confirm each cron job is firing
- Area trend of response time for capacity planning
- Same hits feed both the chart and triage table views
Features
What SleekView Charts gives you for EasyCron
External cron, internal dashboard
Render EasyCron's pings as Number, Pie, Bar and Area cards on the receiving WordPress install. Ops sees what really happened, independent of the third-party UI.
Failures as their own queue
Filter to status >= 400 and the chart cards and triage table both narrow to failing pings. A degraded endpoint stops hiding inside thousands of healthy hits.
Share with the team that runs the site
Export the hits behind a card as CSV or share the dashboard URL with whoever owns the WordPress install. Conversations with hosting and dev teams stop relying on EasyCron logins.
Audience
Who builds EasyCron charts dashboards with SleekView
Site reliability
Pin a failed-pings view to the dashboard, scoped to the last 24 hours. Recurring 502s or timeouts on a specific endpoint stop hiding inside thousands of healthy hits.
Performance leads
Trend average response time per endpoint to spot a checkout-cron call slowing month over month before it crosses the timeout and starts dropping orders.
Client teams without EasyCron access
Hand a client a read-only WordPress dashboard that shows whether their scheduled tasks are actually running. The EasyCron account stays inside the agency, the answer is shared.
The bigger picture
Why external cron needs an internal dashboard
EasyCron exists because wp-cron is fragile, and replacing it with a real scheduler is one of the highest-leverage moves on any production WordPress site. The trade-off is that the scheduler now lives outside the install and the only proof of work is the HTTP call that lands on a URL. The receiving side typically sees nothing structured, just access log lines mixed in with normal traffic.
SleekView Charts gives those calls a structured place to live by way of a tiny mu-plugin shim and a captured table. The result is a Number card of pings, a Pie of status codes, a Bar of per-endpoint activity and an Area of response time, all readable on the same WordPress admin that the rest of the site is run from. EasyCron's UI stays where it is for scheduling.
The WordPress install gains a measurable surface for what actually happened, which is the conversation ops, agencies and clients actually need to have.
Questions
Common questions about SleekView Charts for EasyCron
Nothing. EasyCron carries on calling URLs on the schedule you set. The captured table is populated by a small mu-plugin on the WordPress side that matches incoming requests against the EasyCron user agent or a shared secret query parameter and writes one row per call.
No. SleekView never modifies the request itself and never responds in EasyCron's place. The shim observes incoming calls and records them. EasyCron still gets whatever response your endpoint normally returns, and its own retry logic works exactly as before.
Yes. Group by hit_at with an Area or Line card and an Average aggregation on duration_ms to see response time per hour, day or week. Useful for spotting a slow drift on a checkout or reporting cron before it starts hitting the EasyCron timeout.
Yes. Group by status with a Pie or Bar card and the 4xx and 5xx buckets surface as their own slices. Combine with a filter for status >= 500 and the rest of the dashboard scopes to the failing pings only.
Yes. A Bar card grouped by endpoint shows how many times each scheduled URL was hit. Confirms a cron job is actually firing at the expected frequency and exposes endpoints that have quietly stopped being called.
No. EasyCron stays the scheduler. SleekView Charts is the observability layer on the receiving end. Schedule new jobs in EasyCron's UI as you always did, and use SleekView to watch what those jobs are actually doing once they land on the WordPress install.
Yes. Dashboards can be gated by WordPress capability or shared as a read-only URL. Developers can read the external-cron health view without needing an EasyCron login or any of the credentials the agency keeps inside the account.
Yes. Any filtered set behind a chart card exports as CSV. Useful for post-mortems on a failed scheduled job, or for proving to a hosting provider that the external pings actually arrived at the expected rate.
Pricing
More than 1000+
happy customers
Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.
Lifetime ♾️
Most popular
EUR
once
- Unlimited websites
- Lifetime updates
- Lifetime support
...or get the Bundle Deal
and save €250 🎁
The Bundle (unlimited sites)
Pay once, own it forever
Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.
What’s included
-
SleekAI
-
SleekByte
-
SleekMotion
-
SleekPixel
-
SleekRank
-
SleekView
€749
Continue to checkout