Author Topic: Auto discovered dci deleted once wireless ap client unreachable  (Read 330 times)

Egert143

  • Full Member
  • ***
  • Posts: 120
    • View Profile
Auto discovered dci deleted once wireless ap client unreachable
« on: December 07, 2019, 09:53:23 pm »
Hello

I am having litle bit of trouble with template monitoring. With template auto apply rule device is added to template, for example wireless ap. Inside template there are few dcis, some for ap itself, some for ap clients. Problem is when some client disconnects its dci wil turn into unsupported and is automaticaly removad and once it connects again new dci is auto generated. That effectivly deletes all collected history and fills alarm windows with "status of dci xxx changed to unsupported". How could it be awoided, once dicovered keep it until user deletes?


Tatjana Dubrovica

  • Global Moderator
  • Sr. Member
  • *****
  • Posts: 268
    • View Profile
Re: Auto discovered dci deleted once wireless ap client unreachable
« Reply #1 on: December 08, 2019, 02:20:33 pm »
There is no option to make instance discovered DCIs only user deletable, but you can set instance retention mode to custom and define how many days missing instances should be kept.

Egert143

  • Full Member
  • ***
  • Posts: 120
    • View Profile
Re: Auto discovered dci deleted once wireless ap client unreachable
« Reply #2 on: December 08, 2019, 07:26:40 pm »
Thanks that seems to be the solution. Usualy monitoring softwares show caps in data when polling was unavailable, not delete entire history. With costum instance retension set to same as data retention time it does exactly this.

Tatjana Dubrovica

  • Global Moderator
  • Sr. Member
  • *****
  • Posts: 268
    • View Profile
Re: Auto discovered dci deleted once wireless ap client unreachable
« Reply #3 on: December 09, 2019, 01:03:07 am »
You can set it in server configuration - then it will be the default behaviour of the whole system.
It was done as it was assumed that either node has connected and have all DCI's or it has no connection, so that users do not need to make any manual actions if instance gone.