OMS – Error "Run Login-AzureRMAccount to Login" e.g. OMS Cmdlets

error-red-key-595x335

I wanted to play with the OMS cmdlets which are part of the AzureRM modules. The OMS / OperationsInsights module itself is called AzureRM.OperationsalInsights. A good place to start with OMS native PowerShell cmdlets is a blog post on the Building Clouds blog. So what is the exact issue? Well, I tried to query my workspace for installed solutions. First I logged in using the Login-AzureRmAccount  cmdlet which succeeded quite nicely..

image

…after I authenticated I ran a cmdlet to get the solutions from OMS…

image

..no matter which cmdlet I tried, I always received the error above.

After some time, I tried to update the modules, running Update-Module which ended in this error…

image

Next step, I tried to install the entire ARM modules by running Install-Module AzureRM –AllowClobber, which ended in a similar error…

image

Continue reading

OMS – Custom Solution “SCOM Effective Configuration”

I had been very busy lately so this blog has been quite for few days, but now I would like to provide a custom OMS solution. My goal was to build a solution which shows you the effective configuration of a monitor or rule, based on a group of objects in SCOM. I created two parts, one is a PowerShell module to collect all the data from your SCOM management server and ingest it into your OMS workspace. For visualizing the data I created a OMS view which looks like this…

screenshot

How does it work? Great question, so let’s start with the data collection.

SendEffectiveConfiguration PowerShell Module

I published the module on PowerShell gallery, which you can find here.

The module supports the following parameters:

  • GroupDisplayName

This parameter accepts any existing group in SCOM, that contains objects. E.g. Windows Server 2012 Computer Group.

  • ManagementServer

Set your SCOM management server here.

  • CustomerID

CustomerID is the workspace id where you want to analyze your data.

  • SharedKey

SharedKey ist the primary key for the corresponding workspace.

So the command executed would look like this:

Send-EffectiveConfiguration -GroupDisplayName  “Windows Server 2012 Computer Group” -ManagementServer SCOM -CustomerId [WorkspaceID] -SharedKey [PrimaryKey] –verbose

Continue reading

OMS – HTTP Data Collector API 403 (Forbidden)

Few weeks ago Microsoft released the Azure Log Analytics HTTP Data Collector API, which allows you to shoot JSON data into OMS Log Analytics. This is awesome news, because now anything is possible. This means, you are able to use (m)any script languages to send any data to OMS for further analytics and you are able to use all the nice OMS goodies like alerting, view designer for building awesome dashboards, query language for some deep dive into your data etc. I had been playing with this API on my Linux box to see what it is capable of. I use a PowerShell test script on Linux, which I knew worked before. All of a sudden I received this error…

image

I was wondering, because I was sure this script and my workspace is working fine. Actually I modified the script from this blog post here Azure Log Analytics HTTP Data Collector API. If I check the error code it says that workspace ID or connection key needs to be valid.

image

After a minute I got an idea and compared the time on my Linux box…

1

..and the one on my client…2

..so there is a deviation of 40 minutes. I corrected the time on my Linux machine and all of a sudden the data submission worked fine. I was wondering, what the maximum allowed deviation will be . I went back in time in 5 minutes steps and after I reached a 15 minute time difference I received the same error. If I put the time back just 14 minutes, the script worked fine.

Conclusion: If you are playing with the Azure Log Analytics HTTP Data Collector API  make sure your clock is set correctly otherwise you will receive a 403 error.

OMS – Intelligence Packs Cheat Sheet

image

Operations Management Suite (OMS) is one of the (probably) hottest technologies Microsoft is currently working on. If you want to bet on a horse, which will win the crazy technology race now and in the future, OMS will be a save choice. Because of that I highly recommend start using and learning OMS today. There are plenty of sources on the internet to get you started.

OMS uses solutions / Intelligence Packs to add functionality, logic, data and visualization to OMS. As soon you add a solution to OMS, files are downloaded (but not in all cases) to your server where the Microsoft Monitoring Agent is installed. These files look like SCOM management packs and the internal structure is also similar. In a lot of cases, these management packs contain collection rules which are executed at a certain interval. For OMS you can choose two different ways , either you just use the Microsoft Monitoring Agent (MMA) in a “agent only” scenario or you are using the Microsoft Monitoring Agent in conjunction with SCOM. In both situation you will be able to collect data, but not in both situation you will be able to use all solutions, because some solution(s) require a SCOM management group. Another interesting finding is, that not all data gathering processes use the same “methods”. E.g. some solutions just execute PowerShell to gather event and log entries, which will be sent to OMS other solutions use a lot of bundled DLL files to deliver sophisticated data collection. I was interested in getting a kind of an overview, which solution uses what “technology” to collect the information from your systems and what targets are these collection rules using. I did basic investigations, like first activating a solution in the OMS portal and then I checked out what management pack got downloaded to SCOM. After figuring this part out, I checked the management pack itself to see what rules and assemblies it contains etc.

Because every management pack behaves different, I tried to put the most important information into a cheat sheet. I know the solutions will change rapidly and new solutions will come out. But I think for having a first overview / impression, it will help in certain meetings or troubleshooting scenarios.

You will find some deeper information like the following:

  • All rules involved in the data collection process
  • The target class the rules are using
  • What resources (DLL, execpkg) files are used?
  • How frequently the data gets collected (interval)?
  • Are there RunAs profiles involved?
  • What technologies are supported?
  • Agent requirements, MMA only or MMA + SCOM?
  • The solution title is a hyperlink to TechNet article
  • The intelligence pack title is a hyperlink to SystemCenterCore.com which will show all IP / MP details

Let me know if you have any comments, updates or ideas. I will try to frequently update this sheet. You can download the PDF from TechNet here.

OMS – Agent for Linux Troubleshooting Help

In my previous post I introduced the OMS Agent for Linux. This time I would like to give you some troubleshooting starting points. There are countless possibilities for errors to occur, so it is nice to have at least a consolidated list where to find a log or configuration file. This should give you a pretty good overview of the most important places to look for. For detailed configuration scenarios read the documentation on GitHub .

Documents-icon

Log file paths:

Continue reading

OMS – Agent for Linux Installation (Preview)

Operational Management Suite (OMS) is probably the final product of a long evolution process starting back in 2011 known as System Center Advisor, later on transforming into Microsoft Azure Operational Insight and finally into a growing management suite for Azure and on-premise services. Read my post here for more historical information on this awesome solution.

I think it is a historical move for Microsoft to support Open Source and Linux track the relationship goes even that far, Microsoft writes “love blog posts (not love letters :))” Microsoft Loves Linux, read the blog post series here. Because of that I would like to show how OMS supports Linux data collection.

The OMS Agent for Linux enables rich and real-time analytics for operational data (Syslog, Performance, Alerts, Inventory) from Linux servers, Docker Containers and monitoring tools like Nagios, Zabbix and System Center

Currently this Linux agent is in a preview stage and supports at this very moment the following operating systems…

  • Amazon Linux 2012.09 –> 2015.09 (x86/x64)
  • CentOS Linux 5,6, and 7 (x86/x64)
  • Oracle Enterprise Linux 5,6, and 7 (x86/x64)
  • Red Hat Enterprise Linux Server 5,6 and 7 (x86/x64)
  • Debian GNU/Linux 6, 7, and 8 (x86/x64)
  • Ubuntu 12.04 LTS, 14.04 LTS, 15.04 (x86/x64)
  • SUSE Linux Enteprise Server 11 and 12 (x86/x64)

As things move fast this list will change within the next weeks / months. Keep an eye on GitHub where you find up-to-date information.

The amazing thing is, that the agent is built on open source components and for collecting the data and the aggregate it uses FluentD . FluentD has hundreds of existing plugins, which will make it really easy for you to add new data sources. So this perfectly to collect whatever data you want.

Continue reading

NiCE Datacenter Tag 2015 – Session “Operations Manager Dashboards – Neue Widgets und Möglichkeiten”

image

This blog title looks probably a bit strange to you because it is in German. The company NiCE is organizing a “Datacenter Day” in Munich and there will be all kind of topics presented by Microsoft, partners and people from the community. I will be having a session about the new widgets and its capabilities in SCOM called “Operations Manager Dashboards – Neue Widgets und Möglichkeiten”.

According to Microsoft, 60% of System Center customers are actively using System Center Operations Manager (SCOM) today. While there are many different System Center events available, only a handful of them focus predominantly on SCOM and new products like Azure Operational Insights (OpInsights) for big data analytics. As a leading System Center ISV in Germany, NiCE will be hosting an event in conjunction with Microsoft to address the above mentioned gap. The objectives of the event include:

  • Present and discuss the latest developments and news on SCOM and OpInsights
  • Hands-on tips and tricks for using SCOM in large environments
  • Illustration and recount of the common System Center integration scenarios
  • Present partner extensions for System Center
  • Provide top content in German for the DACH region

The detailed agenda looks like this (subject to change):

image

If you are interested in attending this event it will held on:

February 17th 2015 at Microsoft München,Konrad-Zuse-Straße185716 Unterschleißheim.