Hi Dojo,
I have a question, that derives from this thread.
I would like to use the alarm state of a view (respective the highest severity of alarms in all views below that view) as variable in an automation script. Is there a method to retrieve that value from a view? This should then finally used to set a value of a property for this view.
My scripts looks like this and is working well with a fixed value instead of the alarm severity variable and includes some exception handling already.
public class Script
{
public void Run(Engine engine)
{
ViewInfoEventMessage[] allViews = GetViews();
if(allViews == null)
{
engine.ExitFail("No views were found");
}
foreach(ViewInfoEventMessage view in allViews)
{
// do the filtering of views you want to update
if(view.Name.Equals("ABC"))
{
UpdateViewProperty(view,"ABC","12345",engine);
}
}
}
public void UpdateViewProperty(ViewInfoEventMessage view, string propertyName, string propertyValue, Engine engine)
{
SetDataMinerInfoMessage request = new SetDataMinerInfoMessage();
request.bInfo1 = Int32.MaxValue;
request.bInfo2 = Int32.MaxValue;
request.DataMinerID = -1;
request.ElementID = -1;
request.HostingDataMinerID = -1;
request.IInfo1 = Int32.MaxValue;
request.IInfo2 = Int32.MaxValue;
SA sa = new SA();
sa.Sa = new String[] { propertyName, "read-write", propertyValue };
PSA psa = new PSA();
psa.Psa = new SA[] { sa };
request.Psa2 = psa;
request.StrInfo1 = $"view:{view.ID}";
request.What = 62;
SetDataMinerInfoResponseMessage response = engine.SendSLNetSingleResponseMessage(request) as SetDataMinerInfoResponseMessage;
if (response.iRet != 0)
{
engine.GenerateInformation($"Update of property {propertyName} on View {view.Name} was not OK");
}
}
public ViewInfoEventMessage[] GetViews()
{
var getViewsList = new GetInfoMessage
{
DataMinerID = -1,
Type = InfoType.ViewInfo
};
DMSMessage[] dmsma = Engine.SLNet.SendMessage(getViewsList);
if (dmsma == null)
{
return null;
}
return Array.ConvertAll(dmsma, input => (ViewInfoEventMessage)input);
}
}
Could you enlighten me?
Many thanks in advance and best regards
André
Hello again,
looks like the script is doing, what it should do, but the trigger by a correlation rule is very sensitive and triggers the script N times depending on the number of active alarms in that view. I played a bit with various configurations of the correlation rule, but I did not find the right configuration to trigger the correlation only upon change of the alarm level of the view. I thought this might work via alarm grouping, but it doesn't. My current configuration filters for alarm changes (New, escalated, dropped, masked, unmasked), which reduces the sensitive, but this does not resolve the root cause.
In an ideal scenario the correlation rule would only trigger the script when the severity of the view changes. In the recent configuration the correlation rule evaluates all active alarms in the view and triggers the script once per active alarm, that matches the filter / conditions. Thisworks, but is not pretty elegant and unnecessarily consumes processing resources.
In an ideal scenario the correlation rule would only trigger the script when the severity of the view changes. In the recent configuration the correlation rule evaluates all active alarms in the view and triggers the script once per active alarm, that matches the filter / conditions.
Would there be someone who could imagine of a script condition, to filter out only changes on the highest severity in the view?