Learning

Hi Enver, Yes, this is the expected behavior with feeds, as the framework prevents feeding the same value twice. For now, I recommend synchronizing the viewport of the timeline with …

Yes it’s a viable option because we receive multicast localy on each element and send to other element to secure ingest. The monitoring triggers to swith to other input We …

Hi Nick, It looks like the client version you provided is 10.4.5, which explains the issue. The RegexMatch functionality was introduced in version 10.4.8 (see docs), so the 10.4.5 Cube …

Hi Jamie, According to the documentation it seems that it is not possible: Canceled: If a booking is not running yet, it can be forced to transition to this state. …

Hi Pedro, In this case, the best approach is to update the ‘Root Time’ column rather than ‘Time’ column. In that way a user can distinguish between: When the alarm …

Hi Stijn, That is currently not possible with IDP. IDP will allow you to create the element in a specific agent but there is currently no support to decide where …

We didn’t test if this is possible with Docker. Should dive deeper into the networking stuff there to be able to test it. Alternatively, we did test it with Windows …

Hi, I believe this is expected behavior. Checking DataMiner Docs (forbidden characters) you will find that ‘/’ (slash) is a forbidden character. Hope it helps.

Hi Min, 1) I would expect that the backups are stored in the folder you configured(C:\Skyline DataMiner Backups). 2) Can you check the information events and the history of the …

Hi Matthijs, Indeed, a custom operator sounds like the way to go here. You can sort the alarms by time in descending order and return the first root alarm you …

Hi Jochen, The filter you provided should actually work fine. I just tried it out on my local dev agent and it seems to be working as expected. Even with …

As Alexander mentioned, this does indeed seem to be an exception that is thrown inside the installation script. I tried this on my local development agent running a dev build …

Had a chance to dig deeper on the affected agent, Running the Scheduled task directly from Windows Scheduler also was not successful: This error was logged: == Task Scheduler successfully …