What monoscope-tech/monoscope shipped
Written by FoxPlug from the repository's own releases; not affiliated with Monoscope. Paste your own repository in the box below and FoxPlug writes the same weekly update for your product. This page is an automatic summary of the releases, pull requests and commits in github.com/monoscope-tech/monoscope; Monoscope did not write it and does not use or endorse FoxPlug. Every line links to the change it describes.
Get a weekly update like this for your product, free
Week of November 2, 2026
What shipped
- Slack alerts now use one card layout for every alert type, with issue lifecycle updates in the thread and agent answers formatted for Slack. Pull request #810
- Agents across Slack, web chat, schedules and project events now share one capability catalog, authority evaluator, executor and operation ledger. Pull request #619
- UI updates include a searchable dashboard picker, a revised issue page, infrastructure pages, a RUM network tab and repository views. Pull request #808
- Alert noise is reduced: monitor flaps go to the Slack thread only, stale reminders decay, and Issues sort by activity. Pull request #779
- Dashboards now show peak values for latency and percentage charts, drop the /min rate, and display zero errors plainly. Pull request #807
- Dashboard polish adds a stale-data warning chip, sparklines that fit their data, decimal precision on stats and table cells, and consistent latency axis units. Pull request #806
- Connecting Slack now installs the Slack investigation routine, leaving existing installations as their owner set them. Pull request #793
- Fixes include re-invited members keeping their set permission, the free-tier owner, the Discord replay window, a golden flag and test-harness error swallowing. Pull request #786
- The CLI bulk ack command now works for log patterns and maps ack and unack for every resource. Pull request #780
- The CLI prints UTF-8 output under any locale, and --assert fails on undecodable responses. Pull request #782
Why it matters
This week brought a unified alert card in Slack and a shared agent system across Slack, web and scheduled jobs, so alerts and agent responses are consistent wherever you see them. Dashboard charts now state what the data means, and several fixes reduce alert noise and correct permissions and CLI behaviour. Together these changes make daily monitoring and investigation more predictable.
Changelog entry
- Slack alerts use one card layout for every alert type, with issue lifecycle in the thread and agent answers that read well in Slack. Pull request #810
- Slack, web chat, schedules and project events share a capability catalog, authority evaluator, executor and operation ledger. Pull request #619
- UI pass: searchable dashboard picker, revised issue page, infrastructure pages, RUM network tab and repositories. Pull request #808
- Duration and percentage charts headline their peak, drop the /min rate, and error widgets read 0 errors. Pull request #807
- Stale refreshes show a warning chip, sparklines fit their data, stat cards and table columns support decimals, and latency axes use one unit. Pull request #806
- Monitor flaps alert only in the Slack thread, stale reminders decay, and Issues sort by activity. Pull request #779
- Connecting Slack installs the Slack investigation routine; reconnecting leaves an existing installation as set. Pull request #793
- Fixes: re-invited members keep their set permission, plus free-tier owner, Discord replay window, golden flag and test-harness error fixes. Pull request #786
- CLI bulk ack works for log patterns, mapping ack and unack for every resource. Pull request #780
- CLI writes UTF-8 under any locale, and --assert fails on undecodable responses. Pull request #782
- AI search no longer returns 403 on the public demo project. Pull request #787
- OTLP logs whose API key arrives only in the request header are kept instead of silently dropped. Pull request #772
This week: one Slack alert card for every alert type, agents unified across Slack, web and schedules, clearer dashboard peak values, less alert noise, and fixes for re-invite permissions and CLI bulk ack.
This week Monoscope saw a set of changes for people who monitor and investigate issues. Slack alerts now share one card layout for every alert type, with issue lifecycle updates in the thread, and agents across Slack, web chat, schedules and project events now share one capability catalog and executor. Dashboards show peak values for latency and percentage charts, drop the /min rate and read zero errors plainly, with a stale-data warning chip and sparklines that fit their data. Alert noise is reduced: monitor flaps stay in the Slack thread, stale reminders decay and Issues sort by activity. Fixes cover re-invited member permissions, free-tier ownership, the Discord replay window, CLI bulk ack for log patterns and UTF-8 CLI output under any locale.
Week of October 12, 2026
What shipped
- Hasql write and read retries are now bounded by deadlines instead of attempt counts, so a slow TimeFusion deploy cannot push batches into the dead-letter queue. Pull request #676
- Related API change issues now group by service, host, and breaking or incremental classification, and expanding a group keeps endpoint links and bulk selection. Pull request #673
- JSON-path filters that compare a field against a boolean now render the boolean as text, so queries like attributes.app.flag == true no longer fail with a type error. Pull request #674
- Adjacent event lookups on the issue page now order by timestamp rather than distance, which returns the same results without the extra ordering work. Pull request #672
- Adjacent hash event lookups now use the per-hash rollup when no nearby event exists, instead of reading a whole day of raw events. Pull request #675
Why it matters
This week fixed several lookups and filters that failed or ran slowly in production: boolean JSON-path comparisons errored out, adjacent-event and adjacent-hash lookups were slow, and a slow deploy could dead-letter write batches. Retries are now bounded by deadlines, and API change issues are grouped so the inbox is easier to scan.
Changelog entry
- Bound Hasql write and read retries by deadlines so a slow deploy cannot dead-letter batches. Pull request #676
- Compare JSON-path fields with booleans as text so filters like attributes.app.flag == true no longer fail with a type error. Pull request #674
- Order adjacent-event lookups by timestamp instead of distance. Pull request #672
- Use the per-hash rollup for adjacent hash event lookups when no event is nearby, instead of reading a full day of raw events. Pull request #675
- Group API change issues by service, host, and breaking or incremental classification, keeping endpoint links and bulk selection when a group is expanded. Pull request #673
This week: Hasql retries are bounded by deadlines so a slow deploy cannot dead-letter batches. Boolean JSON-path filters no longer fail with a type error. Adjacent event lookups got faster, and API change issues now group by service and breaking or incremental.
This week's changes to Monoscope: Hasql write and read retries are now bounded by deadlines rather than attempt counts. A TimeFusion deploy that refused writes for 45s pushed 24 batches into the dead-letter queue, because the retry budget only bounded backoff sleeps. Every retry now has a deadline. JSON-path filters comparing a field against a boolean now render the boolean as text, so queries like attributes.app.flag == true no longer fail with a type error. Adjacent event lookups on the issue page now order by timestamp instead of distance, returning the same results without the extra ordering work, and use the per-hash rollup when no event is nearby instead of reading a full day of raw events. API change issues now group by service, host, and breaking or incremental classification, and
Week of September 28, 2026
What shipped
- Runtime issue lists now use event timestamps instead of record updates, preventing old errors from moving above active ones after metadata changes. Pull request #646
- Runtime issues sort by their latest error event, fixing cases where recent errors were buried beneath older record timestamps by up to 129 days. Pull request #644
- Dashboard CPU charts no longer fail when PostgreSQL returns numeric types; the Infrastructure dashboard query execution now succeeds. Pull request #645
- OpenTelemetry HTTP spans are normalized across server and client SDKs, storing canonical endpoint templates and improving endpoint analytics filter performance. Pull request #631
- Issue volume charts now serve wide time windows from hourly stats rollup instead of querying the full dataset, reducing latency on issue pages. Pull request #623
- Log Explorer preload retries once on empty responses, recovering from transient failures before the log list consumes the data. Pull request #642
- Grouped dashboard PNG charts render correctly; ECharts axis callbacks no longer access unbound context and all labels appear when data is available. Pull request #640
- RUM and infrastructure data now use consistent vital populations and time windows; live refresh no longer cancels initial loads or orphans chart updates. Pull request #604
- Dashboard widget editing and monitor setup preserve chart previews during scrolling and maintain settings across saves. Pull request #626
- Shared dashboard URLs no longer carry stale endpoint filters; filter values recompute from current endpoint variables on load. Pull request #633
Why it matters
This week's fixes address sorting and timing bugs that affected issue visibility and chart correctness across production data. Normalization of OpenTelemetry spans and performance improvements to issue charts make dashboards more reliable and faster. Several dashboard UI and data consistency issues ensure investigation experiences remain accurate when filters and live updates are applied.
Changelog entry
- Use stored event time when issue pattern is absent Pull request #646
- Decode numeric SQL results in charts Pull request #645
- Order runtime issues by latest error event Pull request #644
- Track latest runtime error event for issue details Pull request #643
- Normalize OTel HTTP spans and speed endpoint analytics filters Pull request #631
- Issue volume charts: serve wide windows from the hourly stats rollup Pull request #623
- Retry Log Explorer preload after empty response Pull request #642
- Fix grouped widget PNG rendering Pull request #640
- Fix stale endpoint dashboard filters in shared URLs Pull request #633
- Improve RUM and infrastructure data correctness and live updates Pull request #604
- Fix dashboard widget editing and monitor setup Pull request #626
- Retry Tagify after script load failures Pull request #641
This week: runtime issues sort by latest error event, not record updates. Dashboard charts handle numeric SQL types. OpenTelemetry HTTP spans normalize across SDKs. Issue volume charts now use hourly stats for speed.
This week we shipped sorting fixes for runtime issues (preventing old errors from reappearing), better handling of PostgreSQL numeric types in charts, and normalization of OpenTelemetry HTTP spans across SDKs. Issue volume charts now use hourly rollup stats for faster loads. RUM and infrastructure dashboards maintain consistent vital populations and time windows, while live refresh no longer interferes with initial page loads. Several dashboard UI consistency fixes ensure investigation views remain accurate.
Week of September 21, 2026
What shipped
- Log list now escapes dangerous characters in ingested log bodies to prevent stored XSS attacks, and summary highlighting only emphasizes values after quoted JSON keys. Pull request #602
- Dashboard variable dropdowns now stay within the viewport by anchoring to the chip's right edge and capping their width. Pull request #603
- Endpoint widgets now share complete SQL results across both JSON and streaming requests, eliminating duplicate backend queries. Pull request #596
- Issue page release markers now persist across data refreshes instead of being wiped by the first response. Pull request #601
- Dashboards now default to @everyone team assignment with a one-time migration for existing unassigned dashboards. Pull request #598
- Dashboard bulk assignment now opens a team picker that preserves assignments after reload, and widget monitors can be independently created and edited. Pull request #597
- Dashboard variable pickers now resolve selected endpoint hashes to their method/path labels and preserve tags after HTMX swaps. Pull request #595
- Virtualized log rows now respond immediately to column resizing and loading states display more consistently. Pull request #594
- Dashboard variables now refresh out of band after selection and remain populated during tab navigation with proper Tagify initialization. Pull request #592
- Issue details page receives improvements to assignment, merge, and step workflows. Pull request #599
Why it matters
This week focused on stability and user experience across dashboards and logs. Security improvements protect against XSS attacks, caching changes reduce unnecessary backend queries, and UI fixes ensure controls stay functional during navigation and resizing.
Changelog entry
- Security: Escape &<> in ingested log bodies to prevent stored XSS Pull request #602
- Log list: Summary highlighting only emphasizes values after quoted JSON keys Pull request #602
- Log list: Sticky cells are now opaque and embedded lists fit properly Pull request #602
- Dashboard variable dropdowns anchor to chip's right edge and cap to viewport width Pull request #603
- Endpoint widgets share complete SQL results across JSON and streaming requests Pull request #596
- Issue page: Release markers persist across data refreshes Pull request #601
- Dashboards default to @everyone team assignment with one-time migration Pull request #598
- Dashboard bulk assignment preserves team selections after reload Pull request #597
- Widget monitors can be independently created, edited, and removed on shared templates Pull request #597
- Dashboard variable pickers resolve endpoint hashes to method/path labels Pull request #595
- Dashboard variables refresh out of band and persist during tab navigation Pull request #592
- Virtualized log rows respond immediately to column resizing Pull request #594
This week: XSS protection in logs, smarter caching for endpoint queries, dashboard variables that work across tabs, and UI fixes for dropdowns, assignments, and rendering.
Monoscope shipped 10 PRs this week focusing on reliability and experience. Security improvements protect log data from XSS attacks. Caching enhancements eliminate duplicate endpoint queries. Dashboard variables now persist across tab switches and stay within view. UI fixes address dropdown positioning, assignment workflows, log rendering, and control state management across HTMX swaps.
Week of September 14, 2026
What shipped
- Fixed bin-width dropdown in the visual query builder to use seconds instead of minutes, eliminating silent 60x bucketing errors. Pull request #589
- Routed RUM session core queries before bounded enrichment to enable TimeFusion to use sessions rollup. Pull request #581
- Fixed dashboard sticky variable layering to isolate widgets below the sticky row and keep ECharts tooltips local to grids. Pull request #591
- Fixed successive dashboard variable prompts by normalizing empty query values and continuing prompts after parent selection. Pull request #590
- Classified TimeFusion handoff errors as transient to retry writes instead of sending batches to the DLQ. Pull request #575
- Fixed endpoint rollup hash expansion on TimeFusion by removing correlated UNNEST that the planner rejected. Pull request #577
- Preserved environment, service, trace, and time context across explorer navigation. Pull request #583
- Fixed dashboard create to use the explicit project endpoint instead of empty htmx URL resolving to 405. Pull request #588
- Kept Slack alerts flowing by fixing root recovery and rendering all alerts through one renderer. Pull request #565
- Retained unboxed centroid vectors across database loading to reduce allocation in canonical-pattern loading. Pull request #555
Why it matters
This week addressed critical query correctness issues, dashboard interaction regressions, and production alerting failures. Several fixes target TimeFusion integration, which improves query routing and reliability.
Changelog entry
- Fix: query builder bin-width dropdown now uses seconds to match KQL parser expectations Pull request #589
- Fix: dashboard sticky variable layering and ECharts tooltip isolation Pull request #591
- Fix: successive dashboard variable prompts with empty value normalization Pull request #590
- Fix: dashboard create endpoint routing Pull request #588
- Fix: conversation title form field namespacing Pull request #587
- Improve: route RUM session core before bounded enrichment for TimeFusion rollup Pull request #581
- Improve: preserve telemetry scope across explorer views Pull request #583
- Fix: endpoint rollup hash expansion on TimeFusion by removing correlated UNNEST Pull request #577
- Fix: retry writes through TimeFusion deployment handoffs as transient errors Pull request #575
- Perf: retain unboxed centroid vectors across database loading Pull request #555
- Fix: Slack alerts now resume flowing with unified rendering Pull request #565
Fixed query bucketing errors, dashboard variables, and Slack alerting. Improved TimeFusion routing and endpoint rollup handling. Better explorer context preservation across navigation.
This week's releases fix several production issues affecting queries, dashboards, and alerting. Query builder bin-widths now correctly preserve units, dashboard variables prompt correctly in sequence, and Slack alerts resume flowing with unified rendering. TimeFusion integration improved with better session routing and endpoint rollup handling. Explorer context now persists across navigation.