Categories:

ALL News Events Blog

Diamanti Acquires GroundWork

BLOG POST

Diamanti has completed its acquisition of GroundWork Open Source, Inc., (https://menafn.com/1103626239/Diamanti-Acquires-GroundWork-Open-Source-to-Enable-Kubernetes-Monitoring-and-AI-Driven-Predictive-Analytics).


GroundWork

For GroundWork, the acquisition represents the culmination of years positioning itself as the world’s most powerful IT monitoring company. Diamanti (https://diamanti.com) streamlines Kubernetes applications and data management for global enterprises. This combination creates an organization even better able to serve customers and compete in the global marketplace.

READ MORE > https://diamanti.com/diamanti-acquires-groundwork-open-source-to-enable-kubernetes-monitoring-and-ai-driven-predictive-analytics/


GroundWork Support Portal

BLOG POST

Updated. Modernized. Responsive.

GroundWork Support

www.support8.gwos.com

GroundWork Support provides help when using and administering GroundWork Monitor. You can quickly find documentation for all GroundWork features, troubleshooting tips, how-to articles, and other resources.

Read More


Is GroundWork Monitor affected by CVE-2021-44228? GroundWork routinely scans released and supported versions for critical vulnerabilities.

For example, on Friday, December 10th, 2021 we scanned GroundWork Monitor Enterprise Edition (EE) versions 8.2.0 and 8.2.1 for the Log4Shell CVE-2021-44228 zero-day vulnerability. On Monday, December 13th, 2021 we also scanned versions 7.2.1, 8.1.3, 8.2.0 and 8.2.1 using updated signatures that came out over the weekend. Our engineers also hand-reviewed the systems to see if any known exploitable configurations exist. The results indicate that GroundWork Monitor (EE) 7.2.1 is not vulnerable. While there is a vulnerable version of log4j 2.11.1 in a few containers in version 8.x, there is no opportunity to exploit it remotely. So no action is needed to secure any supported GroundWork Monitor system for this vulnerability.

Read More


GroundWork Monitor Enterprise 8.2.1

BLOG POST

Announcing our latest version GroundWork Monitor Enterprise Edition (EE), 8.2.1, now available for download, offering several enhancements and two additions to the suite of TCG connectors

The GroundWork Team is proud to announce a new update to GroundWork Monitor, version 8. This is the GroundWork Monitor Enterprise Edition (EE) 8.2.1, and will be the last version for the year. We are adding features that you, our loyal customers, asked for, and one or two that we thought you would like in the future. Also, we are rolling all the patch levels we released for version 8.2.0 up into this release as well.

Read More


GroundWork Desk for Help Desk Ticketing

BLOG POST

GroundWork Desk

GroundWork Desk powered by Invicta Software, is a help desk ticketing system now available for GroundWork Monitor Enterprise.

GroundWork Desk for Help Desk ticketing. GroundWork Monitor does monitoring and alerting, but this is only part of what you need to run an IT shop. Engineers, DevOps, and technicians all need to know they are always working on the most important things, without having to think about the relative priority of a given task. That’s why we are adding GroundWork Desk to GroundWork Monitor Enterprise.

GroundWork Desk (powered by Invicta Software) is a help desk ticketing system, closely integrated with GroundWork Monitor. If GroundWork can monitor it, you can get a ticket on it when it needs attention. This new product makes the need for expensive and complex integrations with other help desk products obsolete – just use GroundWork Desk!

Read More


MonitoringThe GroundWork team has reviewed industry analysis of the recent Kaseya VSA incident, and while details are still being revealed, there are some useful take-aways we want to share. In particular, certain aspects of preparedness and indicators of active compromise can be monitored. We also want to talk a little bit about where GroundWork Monitor fits into security monitoring as a whole. 

Read More


Mitigating Alarm Storms using GroundWork Monitor & Mitigating Alarm Fatigue with GroundWork MessengerGroundWork Monitor Enterprise version 8.2.0 offers enhancements that build on the capabilities we have mentioned in past blogs. While all the dependencies, parent-child, and service and host dependencies are present as before, we have gone through our notification system and revamped it with an eye to making it easier to get the right alerts to the right people, with the right methods. 
Read More


Major new version includes quick-start for automated Network Monitoring, supercharged Kafka-powered notification Engine, and APM features for comprehensive Unified Monitoring

SAN FRANCISCOMay 5, 2021 /PRNewswire/ — GroundWork Open Source, Inc., a leading provider of powerful IT infrastructure monitoring software, today announced the general availability of GroundWork Monitor Enterprise version 8.2.0, its flagship all-inclusive monitoring product. A major new version, the on-premises/in-cloud software package includes multiple containerized monitoring source applications, flexible automation for network monitoring, and innovative rapid-deployment notification integration options.

Read More


       

In our previous Blog, we introduced how we use Prometheus and the GroundWork Application Performance Monitoring (APM) connector to instrument a GoLang program to send metrics to GroundWork Monitor Enterprise. In this article, we continue with more Prometheus examples, but this time we demonstrate how to instrument a Java application with Spring Boot for easy monitoring. With just a few annotations, your Spring Boot application will generate metrics in the Prometheus Exposition format, and we will then show how easy it is to send those Spring Boot metrics to Groundwork Monitor.

Read More


How to use BSM to Prioritize Important Issues

We all want our monitoring systems to alert us when things go wrong. While it’s important to get alerts in the event of a failure or latency problem on something specific such as a SQL database, it’s actually just as important to not receive alerts from too many specific sources in the same alerting channel. If our monitoring system starts to fatigue us, we will ignore alerts until the phone calls and Emails from end users start letting us know a service is impaired or unavailable. Our monitoring solution should notify us both about specific failures in general and major issues, so we can differentiate and prioritize.

A single event, such as max processes in use on a database may not in itself be a problem that needs to be addressed on an emergency basis. A combination of events, though, such as a high value of max processes, a large amount of network discards, and slow response time for an http request can indicate a more general problem that is currently impacting the end users. We can easily monitor all of these conditions individually.

Read More