Is there a trigger/way to cross Xmatters workflows?

Not Yet Reviewed

We have a core monitoring setup that handles alerts and notifications for our main infrastructure.

However, we also have smaller customers with specialized needs. For these customers, we have been building custom workflows for each one individually. The end process is always the same - the alerts go through our ticketing system and alerting mechanisms. But making changes to these individual workflows is inefficient, as we have to update each one separately.

Is it possible to implement a layered approach? We'd like to have a front-end workflow that handles the initial processing and normalization of incoming alerts from different sources. This front-end layer could then pass the alerts into a common back-end workflow that encompasses our core ticketing, alerting and logging systems.

This way, we could maintain a single, centralized setup for our core services, while still being able to preprocess and customize the handling of alerts from various customers and monitoring sources. This would make it much easier to manage changes and updates going forward.

0

Comments

1 comment
Date Votes

Please sign in to leave a comment.

  • Yes, implementing a layered approach for handling alerts and notifications is a smart way to streamline your process and improve efficiency.

    Do we need to consider Back-End Workflow Layer?

    (Edited )
    0

Didn't find what you were looking for?

New post