Streamcore, a provider of cloud services delivery assurance solutions, announced new features to its StreamGroomer and SGM solutions, as part of the new 6.0 release, that enable business-oriented and network-aware visibility for application services delivered from a private, public or hybrid cloud, or from traditional data centers.
With the 6.0 release, enterprises can successfully adopt cloud services and rely on Streamcore solutions to supervise service levels, provide showback/chargeback reports to internal customers such as business units, and troubleshoot performance slowdowns.
The deployment of Streamcore products is highly flexible and can match any cloud services delivery model including: in front a corporate centralized Internet access to manage public cloud services (e.g., SaaS), in front of a data center MPLS access to manage the delivery of private cloud services, and even within branch offices to manage a direct access to external cloud services.
Rich Deep Packet Inspection (DPI) and Measurement Engines to Monitor any Public/Private Cloud Application: In this new 6.0 release, Streamcore has reinforced its DPI technology to identify on the network any public or private cloud-based service, with a predefined catalog of more than 400 services (including Salesforce, Citrix GotoMeeting, etc.). An enterprise can automatically enable application performance measurements for any selected cloud-based service. A new end-to-end WAN service level management (SLM) indicator is available to easily detect when the branch network access is the source of performance degradations.
Automated Reports for Showback/Chargeback: New capabilities have been added to the StreamReport application to help the IT team share cloud services performance and usage information with internal customers. The IT administrator can use predefined report templates and create performance dashboards per business unit in a few clicks. Trends can be computed for capacity planning or to detect abnormal application behaviors. When generating PDF reports, open hours can also be taken into account to focus on only relevant statistics for the business.
Integrated per Session Back-in-time Troubleshooting Tools: A session history feature has been integrated into the centralized management to ease troubleshooting for any traditional or cloud-based application. In order to investigate a past event, these new tools provide back-in-time traffic auto-discovery, TopN and per session visibility. This feature takes advantage of Streamcore's DPI engine to auto-discover HTTP/HTTPS applications and to provide advanced information per session (e.g., response time, MOS, hostname/URL, SSL certificate).
Combined Bandwidth Control: When performance issues are caused by network congestion, Streamcore's integrated bandwidth management and behavior-based traffic prioritization mechanisms can be enabled to protect critical applications. In the 6.0 release, these mechanisms have been enriched to automatically manage competition between desktop video flows, and “time-of-day” policies have been added, in particular to change prioritization policies at night time or at the end of a month.
This 6.0 release also includes other improvements:
- New graphical user interface
- StreamMap enhancement to follow an application deployment per branch on a geographical map
- IPv6 traffic monitoring
- Branch appliances additional capabilities: asymmetrical web caching, LAN inventory
“This new release is the most ambitious Streamcore has ever released,” said Bertrand Vincens, Streamcore product manager. “Our customers will be able to experience a smooth transition towards IT-as-a-Service, especially in a hybrid cloud environment mixing public and private cloud services. Combined with our business-oriented approach, we have the most innovative solution on the market for enterprises that have embraced the cloud services model.”
The Latest
Like most digital transformation shifts, organizations often prioritize productivity and leave security and observability to keep pace. This usually translates to both the mass implementation of new technology and fragmented monitoring and observability (M&O) tooling. In the era of AI and varied cloud architecture, a disparate observability function can be dangerous. IT teams will lack a complete picture of their IT environment, making it harder to diagnose issues while slowing down mean time to resolve (MTTR). In fact, according to recent data from the SolarWinds State of Monitoring & Observability Report, 77% of IT personnel said the lack of visibility across their on-prem and cloud architecture was an issue ...
In MEAN TIME TO INSIGHT Episode 23, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses the NetOps labor shortage ...
Technology management is evolving, and in turn, so is the scope of FinOps. The FinOps Foundation recently updated their mission statement from "advancing the people who manage the value of cloud" to "advancing the people who manage the value of technology." This seemingly small change solidifies a larger evolution: FinOps practitioners have organically expanded to be focused on more than just cloud cost optimization. Today, FinOps teams are largely — and quickly — expanding their job descriptions, evolving into a critical function for managing the full value of technology ...
Enterprises are under pressure to scale AI quickly. Yet despite considerable investment, adoption continues to stall. One of the most overlooked reasons is vendor sprawl ... In reality, no organization deliberately sets out to create sprawling vendor ecosystems. More often, complexity accumulates over time through well-intentioned initiatives, such as enterprise-wide digital transformation efforts, point solutions, or decentralized sourcing strategies ...
Nearly every conversation about AI eventually circles back to compute. GPUs dominate the headlines while cloud platforms compete for workloads and model benchmarks drive investment decisions. But underneath that noise, a quieter infrastructure challenge is taking shape. The real bottleneck in enterprise AI is not processing power, it is the ability to store, manage and retrieve the relentless volumes of data that AI systems generate, consume and multiply ...
The 2026 Observability Survey from Grafana Labs paints a vivid picture of an industry maturing fast, where AI is welcomed with careful conditions, SaaS economics are reshaping spending decisions, complexity remains a defining challenge, and open standards continue to underpin it all ...
The observability industry has an evolving relationship with AI. We're not skeptics, but it's clear that trust in AI must be earned ... In Grafana Labs' annual Observability Survey, 92% said they see real value in AI surfacing anomalies before they cause downtime. Another 91% endorsed AI for forecasting and root cause analysis. So while the demand is there, customers need it to be trustworthy, as the survey also found that the practitioners most enthusiastic about AI are also the most insistent on explainability ...
In the modern enterprise, the conversation around AI has moved past skepticism toward a stage of active adoption. According to our 2026 State of IT Trends Report: The Human Side of Autonomous AI, nearly 90% of IT professionals view AI as a net positive, and this optimism is well-founded. We are seeing agentic AI move beyond simple automation to actively streamlining complex data insights and eliminating the manual toil that has long hindered innovation. However, as we integrate these autonomous agents into our ecosystems, the fundamental DNA of the IT role is evolving ...
AI workloads require an enormous amount of computing power ... What's also becoming abundantly clear is just how quickly AI's computing needs are leading to enterprise systems failure. According to Cockroach Labs' State of AI Infrastructure 2026 report, enterprise systems are much closer to failure than their organizations realize. The report ... suggests AI scale could cause widespread failures in as little as one year — making it a clear risk for business performance and reliability.
The quietest week your engineering team has ever had might also be its best. No alarms going off. No escalations. No frantic Teams or Slack threads at 2 a.m. Everything humming along exactly as it should. And somewhere in a leadership meeting, someone looks at the metrics dashboard, sees a flat line of incidents and says: "Seems like things are pretty calm over there. Do we really need all those people?" ... I've spent many years in engineering, and this pattern keeps repeating ...