Global research: Security leaders’ priorities for cloud integrity, the talent gap and the most urgent attack vectors.
Proactive troubleshooting for optimized customer experience
Bill One’s teams can now move from reactive troubleshooting to a proactive one. “In the past, an issue only became apparent when we received customer inquiries or when errors occurred frequently,” says Maeda. “Now, we get the alert three minutes after it was set off, and issues are resolved within 30 minutes as we can easily identify the cause of latency, whether it is in the frontend, backend, database, or elsewhere.”
Looking forward, Maeda plans to keep raising awareness about Splunk APM among other teams involved in the Bill One business and give accessibility to more users to encourage usage. “We also want to implement more features using the ID codes assigned to invoices, and even apply Bill One features in areas not covered by OpenTelemetry, such as email transactions,” Maeda adds.
Additionally, Maeda plans to extend the application from troubleshooting to optimize sales, user experience, and customer success. He also hopes to raise general awareness about OpenTelemetry within other teams that support Bill One’s services. “More engineers are curious about OpenTelemetry,” says Maeda. “I’m eager to help them learn more, and if more of them start to evaluate solutions and choose Splunk because it is doing well with us, that would make my day.”
I’m eager to help them learn more, and if more of them start to evaluate solutions and choose Splunk because it is doing well with us, that would make my day.