I'm building out many dependencies using the API and have realized that there are a few thousand "Default" dependencies that could be applied if there were a way to infer there should be a dependency based on naming patterns (or tag attributes).
e.g.
LAWIRELESSAP01
LASWT01
LARTR01
Are there any ways to more dynamically within the platform to ensure that the AP and SWT always have RTR01 as a parent trigger dependency? If I add more devices at the LA site and possibly have a common tag, are there any LLD or Macro capabilities that can ease this administration?
From looking around on forums and Google I haven't found any good guidelines around dependencies and if there are any good tips and tricks for building them out and maintaining them other than programmatically through the API.
I'd love to hear how others are using dependencies and configure them in a medium-large implementation where there can be dependencies between multiple templates.
Thank you for reading and any input!
e.g.
LAWIRELESSAP01
LASWT01
LARTR01
Are there any ways to more dynamically within the platform to ensure that the AP and SWT always have RTR01 as a parent trigger dependency? If I add more devices at the LA site and possibly have a common tag, are there any LLD or Macro capabilities that can ease this administration?
From looking around on forums and Google I haven't found any good guidelines around dependencies and if there are any good tips and tricks for building them out and maintaining them other than programmatically through the API.
I'd love to hear how others are using dependencies and configure them in a medium-large implementation where there can be dependencies between multiple templates.
Thank you for reading and any input!