Skip to main content

Week in review

Hey readers, sorry I haven't been on top of things, but there is too much to keep on top of, and its hard to have time to dump all of this. Now my email has let up…. But the snow is still pouring down I have a few minutes to think and post my thoughts.

We had a great week of progress in my groups on various projects. Here are some of the accomplishments for this week that we had. I will try to post more info on the things we tackle:

  • HP NNM
    • Moved to APA polling, and alarms have been reduced quite a bit.
  • HP RAMS
    • Integration is now working, and defining the paths we want to alarms on.
    • Had some good training, and hopefully the product will start to deliver better value than we have gotten from it in the past
  • HP BAC
    • Still having issues getting events from BAC to flow into OVO for notifications from BPM/Sitescope
    • Implemented a lot of new monitors for up/down to replace some older Spectrum monitoring that was in one of the groups.
    • Looking at RUM in the future, might replace an existing tool and give us better functionality.
  • Sevone
    • Things are in much better shape now, and we are pushing out some additional ACL changes to fix access from one of the Sevone clusters.
    • The install in the UK is progressing well now.
    • The reporting requests are flooding in, so lots of work. We want to educate users to use it themselves, so we can stop being bothered with simple requests.
  • Splunk
    • Working on some smaller issues, the product is bulletproof
  • Opsware NAS
    • Working on 3 annoying/major bugs, making progress on them, support had been slow previously, but thanks to bothering my sales guy things have picked up a lot.
    • I have 2 fixes for some rendering bugs as well, which seem to be in the next patch.
  • Opsware PAS
    • Dev upgrade was botched, but working with support. Will do production once we figure out what the problem is.
  • Vmware Virtualcenter / Platespin
    • Making progress on access and integration. Expanding some of our SQL clusters to take the additional DBs.
  • IBM Director
    • Installed the power monitoring module, its quite nice, same story as everywhere. We have no power.
    • Working on the integration via SNMP into Netcool Omnibus.
  • Netcool
    • Worked on deduplication problems and made other changes. We've been losing events, and its been more problematic recently. This is a major thorn in our side.

Comments

Anonymous said…
I too have noticed that Opsware Network Automation System has been slipping in quality over the last year. We are a large ISP and features that were committed to us, were not delivered in the 7.0 release. The recent minor releases of NAS, are getting unstable by the day.
Unknown said…
Our feature requests have been getting delivered to us. I agree with you that the move to 7.0 has been less than stable, but all of the other versions we ran previously were great. The new integration with NNM, PAS, and NAS are very slick.

Popular posts from this blog

Dynatrace Growth Misinformation

For my valued readers: I wanted to point out some issues I’ve recently seen in the public domain. As a Gartner analyst, I heard many claims about 200% growth, and all kind of data points which have little basis in fact. When those vendors are asked what actual numbers they are basing those growth claims on, often the questions are dodged. Dynatrace, recently used the Gartner name and brand in a press release. In Its First Year as an Independent Company, Gartner Ranks Dynatrace #1 in APM Market http://www.prweb.com/releases/2015/06/prweb12773790.htm I want to clarify the issues in their statements based on the actual Gartner facts published by Gartner in its Market Share data: Dynatrace says in their press release: “expand globally with more than three times the revenue of other new generation APM vendors” First, let’s look at how new the various technologies are: Dynatrace Data Center RUM (DCRUM) is based on the Adlex technology acquired in 2005, but was cr

Vsphere server issues and upgrade progress

So I found out that using the host update tool versus Vcenter update manager is much easier and more reliable when moving from ESXi 3.5 to 4.0. Before I was using the update manager and it wasn't working all that reliably. So far I haven't had any issues using the host update tool. I've done many upgrades now, and I only have 4 left, 3 of which I am doing this weekend. Whenever I speak to vmware they always think I'm using ESX, when I prefer and expect that people should move to the more appliance model of ESXi. With 4.0 they are pretty much on par, and I'm going to stick with ESXi. On one of my vsphere 4.0 servers (virtualcenter) its doing this annoying thing when I try to use the performance overview:   Perf Charts service experienced and internal error.   Message: Report application initialization is not completed successfully. Retry in 60 seconds.   In my stats.log I see this.   [28 Aug 09, 22:28:07] [ERROR] com.vmware.vim.stats.webui.startup.Stat

Misunderstanding "Open Tracing" for the Enterprise

When first hearing of the OpenTracing project in 2016 there was excitement, finally an open standard for tracing. First, what is a trace? A trace is following a transaction from different services to build an end to end picture. The latency of each transaction segment is captured to determine which is slow, or causing performance issues. The trace may also include metadata such as metrics and logs, more on that later. Great, so if this is open this will solve all interoperability issues we have, and allow me to use multiple APM and tracing tools at once? It will help avoid vendor or project lock-in, unlock cloud services which are opaque or invisible? Nope! Why not? Today there are so many different implementations of tracing providing end to end transaction monitoring, and the reason why is that each project or vendor has different capabilities and use cases for the traces. Most tool users don't need to know the implementation details, but when manually instrumenting wi