As we've discussed in the Session Reporting section, Embrace uploads its sessions when the application is backgrounded or, if that fails, on the next app launch. This delay may seem like it hurts the immediacy of the data you are seeing, but the reality is that at scale this still means you are finding out about issues very quickly.
However, some situations might require instant feedback, such as hunting an especially difficult bug, troubleshooting on behalf of high-value users, or monitoring a new version rollout.
You can leverage the log message API for this.
Using the Log Message API
You can log a message immediately by calling any of the
log functions, like
'Loading not finished on time',
Here's a breakdown of the arguments being passed to the
logError method (the only required one is the message):
- message The string is the message itself. Try to make this short yet informative.
- properties This is a map of key-value pairs you can use to categorize and filter log messages with.
- allowScreenshot This indicates whether you'd like a screenshot captured or not (screenshots must also be configured in the Embrace configuration for your app).
You can also adjust the severity of the log by either calling the
Embrace.instance.logWarning("User attempted expired credit card", props);
Embrace.instance.logInfo("User has entered checkout flow");
- The maximum length for a log message is 128 characters. Messages are truncated if they exceed the limit.
- Properties are limited to 10 per log.
- Property keys have a limit of 128 characters.
- Property values have a limit of 256 characters.
Being Alerted on Logs
Once you start using our alerting feature you can also configure how these are handled on the backend. Using the Embrace Dashboard, you can configure email alerts to be sent to your team when certain thresholds are met with log events. For example, let's say you have a steady rate of 1% for a given log event. You could set that as a threshold and receive an email if the rate rises beyond that in a sustained way.
Logging a message using the Log Message API makes a network request immediately. Sending too many logs can easily impact application performance or battery life.
For more tips on making the most of the Log Message API, checkout the Best Practices.
Congratulations! By this point, you should have a solid integration. Continue to the Next Steps page to wrap up your integration.