Search: "business"

Problem == The result of the issue was the business process couldn't use updated information from that specific data stream. Data presented in the business process was outdated for some parts == 3.

Verify with the help of support that the folder is created in the correct location * Assess the impact of upgrades and shut down business-critical processes before performing an upgrade == 5.

Problem == The system was not operational and not functional causing a downtime of the business process to send invoices. == 3. Analysis == === 3.1 Errors in eMagiz === To analyze the problem, we first looked at the errors within the environment to get a sense of the issue at hand.

But as you can see in the following graph, the eMagiz environment is busy for a small amount of time and has little to do in the remainder of the time.

[[image:Main.Images.RCA-Knowledgebase.WebHome@rca-knowledgebase-aws-burst-credits-development-burst-busy-example-graph.png]] [[image:Main.Images.RCA-Knowledgebase.WebHome@rca-knowledgebase-aws-burst-credits-development-burst-impact-on-birst-credit-balance.png]] * Based on the above example, a bandwidth of 1.5 MiB/s should be sufficient to stabilize the Burst balance. * More information on the calculation can be found here: ** [[Metric math explained>>https://docs.aws.amazon.com/efs/latest/ug/monitoring-metric-math.html||target="blank"]] ** [[Using metric math>>https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/using-metric-math.html||target="blank"]] === 3.4 EFS Burst Performance & Calculation === In case of a structural problem with the throughput being used, additional investigation is warranted.