For a lot of Nexthink’s technical professionals, 2020 has been one of the most challenging and rewarding periods of their professional lives. Our customer base was impacted globally by COVID-19, and we were honored to be able to support them whenever and however we could, working closely to leverage their existing investment, as well as developing and distributing tailored services for those that needed them.
After working in enterprise IT for over 20 years, I’ve come to the realization that most departments suffer from the same underlying contradiction. By nature, we IT professionals are a logic-seeking, detail-oriented bunch. Much of our work can take months, if not years, of meticulous planning and research. We find comfort in gazing upon complex, multi-colored scrum boards and searching for answers to problems that any sane person would avoid.
Kubernetes has been successful for a number of reasons, not the least of which is that it takes care of things that application developers may not want to bother with – such as, for example, networking. Multus is a feature that can be used on top of Kubernetes to enable complex networking use cases.
Based on our interactions with buyers evaluating vendors in the AIOps market, much of what we’re hearing chimes with this quote - “What will AI allow us to automate? We'll be able to automate everything that we can describe. The problem is: it's not clear what we can describe.” Stephen Wolfram, computer scientist and physicist.
Certain changes in services or devices can often be misheeded; failure to recognize even subtle changes can later result in unpleasant consequences. Below we list several examples of such incidents; the checks described are rather lightweight and can be run frequently for critical network assets. The cases below assume that any change in current device’ state should be treated as security issue.
Week 4 at Knowledge 2020 expanded the virtual gathering’s breadth and depth, especially when it came to several IT Workflows sessions by top companies around the world. Here are a few highlights from key presentations.
A growing attack surface and the exponential rise of data has opened the floodgates for breaches, leading to increased scrutiny by regulatory agencies. It’s not surprising that in recent years, regulators have had to double down with compliance mandates that are more stringent and punitive than ever before.
So I've only been at Splunk for 8 months, and in the short amount of time I've been here, one of the most common questions I've been asked is “How do I get an alert when Splunk is not receiving logs?". As a matter of fact, if I had $0.05 each time I was asked this question, I would have $0.25! Surprisingly, with this being such an often-asked question, I haven't been able to find much documentation on how to accomplish this using the native features of Splunk.
Is it the middle of Spring already? (And Fall, for our Southern Hemisphere readers!) A lot has happened at Splunk since our last developer updates at .conf19. In case you missed any of the great developer sessions there, grab some time to watch what you missed!
In May 2019, Bloomberg Government reported that Federal agencies planned to move 272 information technology programs to the cloud in FY2020. Fast forward to April 2020 — they reported that there are more than 1,800 federal IT programs that are either migrating or considering migrating to the cloud in fiscal 2021, signifying a rapid increase in cloud adoption in the federal government. How might COVID-19 affect this explosive increase in cloud interest?
