New

• Customer Portal: We're happy to announce the launch of our long-awaited customer portal! Starting today, vendors can publish their SLAs to a customer-facing interface, enabling your clients to track and manage their SLAs effortlessly.

  Key features:

  • Customizable dashboards with your branding and logo

  • Top-level SLA metrics including status, active SLA count, and breach count

  • SLO performance over time charts

  • Dedicated URL for each customer, easily embeddable in your existing product

  

  The customer portal provides critical information that your customers care about, helping them stay informed about your service quality. While this is just the first iteration, plans for future enhancements include:

  • SLA reports

  • incident management

  • information on remediation
    

  You will find a dedicated URL for your customer dashboard on the customer portal which stays accessible while active. Find more details about how to configure a customer portal on our docs!

  

• rated-log-indexer is now source available!! The rated-log-indexer is a powerful tool designed to collect and process logs and metrics from various monitoring solutions and ingest them into slaOS. This indexer supports multiple data inputs, allowing you to centralize your monitoring data for efficient analysis and visualization. We’re launching today with CloudWatch and Datadog support. Check out our Github repo by heading here → https://github.com/rated-network/rated-log-indexer

• Amber code for SLA status: We've introduced a new color code to our SLO performance charts: amber. This new state indicates that an SLO is off target but not yet in breach. By adding this intermediate status, we aim to:

  • Improve awareness of potential issues before they escalate

  • Enable teams to take proactive measures to bring performance back on track

  • Provide a more nuanced view of SLO health

  

• [PR #41] Sentry Setup for rated-log-indexer: We've implemented Sentry SDK support to enhance error tracking and performance monitoring. This integration includes:

  • New configuration options in the application settings

  • Updated rated-config.example.yaml with new fields for logging and output configurations

  • Streamlined overall structure by removing unused and deprecated configurations

Updates

• [PR #45] Multiple indexers sending same key: We've enhanced our rated-log-indexer functionality to allow multiple indexers for the same integration (e.g., CloudWatch) to use the same key for ingestion. This update:

  • Streamlines key management

  • Enables parallel indexer operation without key conflicts

  • Simplifies configuration for multi-indexer setups

• Loader for SLI dropdowns: We've added a loading indicator for SLI field mappings and indexed fields. Instead of displaying an empty list while data is being fetched, users will now see a loader, improving the perceived responsiveness of the interface.

• SLA List UI: The SLA list under a customer is now collapsed by default, allowing for easier navigation and a more optimized view when dealing with multiple SLAs.

  

• CloudWatch Integration Pagination: We've implemented pagination for the list_log_groups function in our CloudWatch integration, improving performance and reliability when dealing with large numbers of log groups.

• SLA Table UI: SLA descriptions on the SLA list page are now available via the info icon (i) next to the SLA title.

  

Fixes

• Create SLA UI fix: When adding multiple SLOs in a SLA, we received reports that some times SLO cards were not aligned appropriately and the delete (x) icon across multiple SLO cards were not aligned. This issue has now been fixed!

• Make Datadog’s logs timestamps UTC: Currently, the timestamp object returned from Datadog is in timezone.localtime, but they index in UTC. We’ve pushed a fix to make sure we convert the local time to UTC before it is ingested by our indexer.

• Datadog Integration Log Parsing: We've resolved issues with log parsing in our Datadog integration, ensuring more accurate and consistent log data retrieval.

• Indexer Retry Behavior: We've addressed issues with the indexer's retry mechanism, improving reliability and reducing the likelihood of data loss during temporary system or network issues.