Search: "business"

With manage, we mean: Stay in control of which alerting tags are used within your project and what they mean * Make tags descriptive in nature * Differentiate who requested the tag (Business, Support, Standard) * Remove tags that are not linked to a trigger anymore == 3.

There are three key aspects you should take into account when managing your alerting tags: * Make tags descriptive in nature * Differentiate who requested the tag (Business, Support, Standard) * Remove tags that are not linked to a trigger anymore To manage your alerting tags you navigate to Manage -> Alerting -> Tags === 3.1 Make tags descriptive in nature === The beneficial nature of having the option to tag certain triggers within alerting is that the tag tells you and those you work with why that specific tag is chosen to be linked to a trigger.

Key takeaways == * There are three key aspects you should take into account when managing your alerting tags: * Make tags descriptive in nature * Differentiate who requested the tag (Business, Support, Standard) * Remove tags that are not linked to a trigger anymore == 6.

To learn about this topic we start with a business question to which we want an answer to make this a little bit more concrete. The business question is as follows: * What were the total sales per event?

. === 3.1 Best practices === * Use the standard as described here to correctly set up the alerting * Always stay in contact with the business, preferable as early as possible on which triggers they deem relevant * eMagiz already provides you, from the start point, with a set of relevant triggers * Always send alerts to generic mailboxes or multiple persons.

Those are used by eMagiz for separate purposes * All business tags are prefixed with Business * Use the deployment plan to tell you which alerts you might need to update based on your Production deployment [[image:Main.Images.Microlearning.WebHome@crashcourse-platform-manage-alerting-in-emagiz--deployment-plan-help.png]] === 3.2 Create or Update alerting === 1.

Understanding Data Pipelines == Imagine you are a global event organizer and want to track which events were hits and misses during the year. To analyze that business question you need a lot of data that tells you something about these events.

This is not only nice when you want to revisit the alerting section but it is also very usefull in communication with the business and with a support desk. This way you can create a common truth surrounding a common language.

The advice would be to analyze whether the current heap memory settings are still valid ** If you see a decrease in heap memory slightly after the spike in CPU this is an indication that the runtime was temporarily busy with garbage collection (a standard process within Java) to free up memory.

In the course, you'll pass through each of the Integration Life Cycle phases to create the integration from business intake to setting the alerts & monitoring triggers after the actual deployment of the integration.