Network Services vs DCI with NetXMS server as the proxy node
-
I have a conceptual question:
What exactly are the advatages of network services? Is using DCIs (Origin=NetXMS Agent) with the NetXMS server as the proxy node not more flexible? So you can use the huge flexibility of ExternalCommands. In network services you can't use custom schedule (yes, on the corresponding service status DCI you can). And a very important disadvantage in my opinion: In templates you can't define network services for nodes (and so you can't use instance discovery either).Maybe I overlook a few advantages of network services.
Thanks for any help. -
This is mostly for historical reasons. Initially we create network services as separate objects with two goals in mind: so they affect node status and so configuration will be a bit easier. Then service check DCIs was added for greater flexibility, but services as objects remains to maintain compatibility and because some people prefers to see them as objects (mostly in small installations). So I would say currently there are no advantages over DCIs.
Best regard,
Victor -
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login