You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note that when there are thousands of bot invocations per day you may want to tune the log level of bots. Given an example of the kind of situations that may generate high-volume bots (e.g. ADT feeds, high-frequency device messages, etc.)
There are two levers for controlling bot log levels (see this PR) a. What type of events are logged (error, success etc) known as auditEventTrigger (see here)
b. Where the events are logged
i. Option 1. To DB so you can see it in the app.
Best practice is to always do this to start, for debugging / testing
ii. Option 2. To log only, not visible in Medplum app but logged - better for high volume
The text was updated successfully, but these errors were encountered:
#2528 introduced the ability to configure bot logging to fit high volume use cases.
The documentation needs to be updated accordingly
Proposed changes in this document: https://www.medplum.com/docs/bots/bots-in-production
b. Where the events are logged
i. Option 1. To DB so you can see it in the app.
Best practice is to always do this to start, for debugging / testing
ii. Option 2. To log only, not visible in Medplum app but logged - better for high volume
The text was updated successfully, but these errors were encountered: