^{Originally posted by dschibster February 7, 2024}
Hi @jongpie,

happy to report that since I presented Nebula Logger at the Salesforce Architects meetup in Düsseldorf, there's hardly a project where I don't see it in use. :)

Right now in one of our projects, we are also using it to log all of our Apex Transactions. However, and this is where things become interesting, we are integrating with MuleSoft. MuleSoft is asynchronously handling the transformation and load into different systems (and Salesforce too). All we get back at the time of sending our payload is a Success.

Of course, we also want to get to know about errors happening in MuleSoft. We were contemplating creating a RestResource for external Systems to give information back to us, for example by creating a new Log (As Parent Log) under the one that triggered the integration itself.

Before we go into further detail creating this ourselves (because architectural guidelines are hestitant about letting us create endpoints), what do you think, would you consider it a worthwile addition to Nebula Logger in general?

BR
Dennis