Learning

Hi Alberto, I was unable to find any publicly available case studies. However, it might be interesting to take a look at the following catalog items: 1. IP Network Explorer …

Hi Arturo, I have it running like this: After the 5min I’m receiving an email.

Hi Arturo, Could you double check that neither the checkbox ‘Autoclear’ (for new correlated alarms) nor ‘Execute on clear’ (for ‘Run Scripts’) is selected? Hope it helps.

Hi Stefan, Note that those general parameters (=parameters added by DataMiner to each element independent of the connector it is using) are a little bit more hidden away. As indicated …

Hi Stefan, If you already double-checked that this general parameter is not monitored in the alarm template, then there is likely something else causing this behavior. I would suggest contacting …

Hi Jarek, I will try to answer your questions: Is this architecture officially supported by Skyline? Yes Is DataMiner Failover using a Virtual Hostname fully supported across a Layer 3 …

Thanks, Pedro. I’ll check things out tomorrow based on the information you provided. By the way, I made a typo and entered “Hiroaysu,” but the correct spelling is “Hiroyasu.” I …

Hi Hiroaysu, An example connector that implements rate calculation logic can be found on the following GitHub repository: SLC-C-Example_Rates-SNMP.

Hi Gunnison, Note that script ResourceScheduling_CreateJob is a MediaOps Plan solution script used for interaction in the LCA. We can’t guarantee that the code will stay backwards compatible (e.g.: additional …

Hello Gunnison, The error you pasted states that the ResourceScheduling_CreateJob script failed due to not having the OnApiTrigger. By default, User-Defined APIs look for an OnApiTrigger function when called. You …

Hi Fernando, Hope you are doing well. I believe GQI is going to be the way to go. I was able to reproduce what you are seeing.  It seems if …

Hi Tobias, What versions of Renci.SshNet and BouncyCastle should I use? To be able to answer this question, I would need to have a closer look at the issue    …

Hi Robert, This is expected behaviour, the GQI runner spawns a separate automation process for every ad-hoc datasource that is used. This is to ensure that issues in one data-source …