By chance I stumbled through this free GUI utility called svfAlarms, which enables you to import and export vCenter Alarms. The author does not provide his name on his blog (he probably does not care about glory… -:) … ). But the tool is useful for persons wanting to quickly import alarms created on other vCenter servers.
Each time you export alarms with this tool, it creates an Alarm Sets. What's that? An Alarm Set is a folder where are placed the individual exported alarms as XML files plus a single Alarm Index XML file. By default the folder is created under the sfvAlarsm installation directory. This file contains a reference to the Inventory where the individual alarms were defined. While mostly defined in root, there might be a situation when there are not only per vCenter, but also other custom alarms defined per Datacenter (there could be a situation where there is two datacenters within single vCenter). So it's quite important to read the User guide, where you'll find out how to deal with this case. You can click to enlarge.
The 32-bit utility is compatible with vSphere 4, 5 and 5.1. A .NET framework 3.5SP1 is required for this tool. You can download this tool from the author's download page, where he provides also a PDF user guide. The utility is provided as an MSI package (Just to let you know, when I checked, the tool had extension *.pps and so after you'll have to rename it to *.MSI, but it installs correctly).
What are The possibilities?
- Import and export vCenter alarms
- Save connection information for several vCenters
- Possibility to Delete all existing alarms during import (Through File > Preferences).
You can see the export directory called Alarms, which is located under the installation directory.
A quick quote from the Users Guide:
There are some 37 default alarms in vCenter 4, 55 default alarms in vCenter5 and 61 default alarms in vCenter5.1 Alarm definitions can be fairly complex and to manage and document alarms, duplicate them across multiple vCenter installations and also to keep a managed state can be time consuming for administrators. The sfvAlarms utility can help simplify the alarm management task.
To Import and Export vCenter Alarms is easy through this utility.
It's rather convenient way of save a different sets of Alarms per vCenter. The use cases are numerous. You might want to test some alarms in non production environment before going into a production environment. So this quick way you can import them into your production environment, by keeping your existing alarms untouched. Other ways of doing this would certainly be the PowerShell way….
Supported versions of vCenter Server
- vCenter 4.0 U3 and U4
- vCenter 5.0 U1 and U1b
- vCenter 5.1
The sfvAlarms utility can be downloaded from this page.
Source: https://stripeyfish.wordpress.com/download/
If you like this post, don't hesitate to share….!!!
Johann Krasinger says
February 12, 2013 at 6:32 pmI just tried this “Alarm-Gui” and i can say thats a tool i was missing a long time. With this GUI i can transfer the Alarm rules from one vcenter to the other in keeping these rules the same on all vcenters. Very nice. The only problematic thing i found was, that this tool is writing the exported data into the “program files” directory, which is definitely not allowed within the company (i know, i can override the rules as an administrator). So my question is, if this behavior can be changed or alternately the target directory can be selected or defined within the preferences?
Thanks for this Tool
jonny
Vladan SEGET says
February 12, 2013 at 7:00 pmThanks for sharing. The author of the tool, if reading my blog, might do a change and release an update?
Best
Vladan
Stripeyfish says
March 2, 2013 at 7:32 pmCheers for sharing the my blog post. I should be able to update to allow user to select a ‘data’ folder from which alarms are imported from or exported to. Will post back when had a mo to re-compile and upload new version.
Vladan SEGET says
March 2, 2013 at 7:45 pmCool, No problem. Keep us updated… -:)
Stripeyfish says
March 7, 2013 at 3:42 amNew version now uploaded 🙂
This is now implemented in v1.1.1 available on Download page of my blog (http://stripeyfish.wordpress.com/download/) along with updated user guide. The export setting is on the Preferences dialogue – you can leave at default or specify custom folder.
Johann Krasinger says
March 2, 2013 at 8:08 pmThats a nice message, thanks in advance.
I do have an additional question, maybe you can answer it. As i am working at an Austrian Company we are using German Language in Windows OS. Administrators however are using english GUI’s for the vSphere Web Client or the vSphere viClient. When i’m exporting the Alarms with the svfAlarms Tool all Alarms are exported in german language. If i now reimport these Alarms these were “translated” to German, and even if i’m using the English GUI theses Alarms will be shown in German. For now i have no idea if this may influence any further upgrades on vCenter ?
Do you have any simple idea how to avoid this translations?
Stripeyfish says
March 4, 2013 at 12:31 amHaven’t looked into localization before, however, on first thoughts when importing the German alarms, they are probably staying in German as not going through any of the vCenter APIs directly but being serialised directly into the alarm classes, hence localization wont be applied, maybe(?). That would be my guess – would have to do some tests.
Thanks for trying out the utility 🙂
Have made the code edits to allow custom export path to be selected in Preferences, just need to test it then will upload.
Stripeyfish says
March 7, 2013 at 3:47 amMulti language support in the core vCenter product I expect uses ‘string tables’ or resource files, so that upon OS language detection, or install language, all the defined strings will use the correct language entries.
Unfortunately when importing Alarms, they always come in as Custom alarms, even if they are exact copies of the original default alarms – hence vCenter effectively knows nothing about them and the string table/resource file lookups wont occur. If you wanted to import as English, then would need to export from English language OS, or manually translate and update the XML files before import 🙁
Johann Krasinger says
March 7, 2013 at 5:48 pmThank you for your detailed description, this is helping me a lot … now awaiting the edited version of your tool.
Thanks for your assistance.
Stripeyfish says
March 7, 2013 at 6:19 pmIts ready and waiting for download! 😀
Johann Krasinger says
March 8, 2013 at 3:33 pmThank you for this quick change – works great.
If my time allows i will start playing around with localization.
Update tool request says
December 3, 2016 at 6:18 pmWould you update the tool which can support vCenter version 6 and 6.5 now?
Would appreciate if you could please.
Vladan SEGET says
December 4, 2016 at 2:54 pmUnfortunately I’m NOT the author -:)
Regards.
Diego Garro says
July 4, 2018 at 3:32 amHi
Currently using this to migrate Alarms from 6.0 to 6.5u2, everything worked like a charm.
Regards
Pascal says
November 20, 2018 at 12:10 amThis tool was magic on the previous version !, but unfortunately, it does not seems to work on VCSA 6.5 anymore . The author web page seems to be down as well. Is anyone has a tool that could replace that one? I need to export all alarms to a XML format or CSV and re-import to another vCenter.
I liked this tool, because I could update the XML files to change the alarms name, the destination cluster / Folder etc.