Monitoring as code with fdmon (Fast Deployment Monitoring)
Since the start of the project, fdmon has relied on an "Everything as Code" model in order to be able to integrate new features as quickly as possible (not having, for example, to redesign the UI to support them).
The initial poor UI ultimately turned out to be the right choice as it triggered a model that is now completely appropriate in terms of deployment and interactions with the surrounding ecosystem. This model has allowed us to quickly expose all the functionality of the solution via its REST API.
The fdmon “Everything as Code” model includes two types of configuration definition : declarative definition and procedural definition. Here are some examples :
领英推荐
Declarative code can be made dynamic thanks to Context Prefixes which ask fdmon to apply a parameter only if a context is valid, the latter being able to itself be dynamic. Moreover, you could turn all declarative definitions into procedural definitions by deploying them from fdmon Orchestration Workflows.
To name a few common use cases, with a simple script using CURL or from any automation or deployment tool, you can redeploy completely and remotely your fdmon monitoring platform, the configuration of a specific item or the Analytics code of any resource associated with a technology.
Unlike most of other solutions on the market, interactions with fdmon do not require using formats such as json or xml, thanks to the extreme simplicity of the fdmon configuration model (parameter/value), which makes learning and DevOps integration of the solution extremely fast.