Today, we’re introducing audit logs in Apollo Studio Enterprise. With audit logs, you can export a data file with key actions taken within your organization.
As your graph scales to more teams in your organization, you need visibility into all of the potential change points on your graph that could affect its stability or performance. We built audit logs to give you more confidence in your graph governance and help you meet any compliance or security requirements.
Use Cases for Audit Log
- Investigate an incident and see what actions lead up to that incident by exporting a log for a time period and graph
- See what actions an individual has taken within a time period
- Investigate your automated systems that are changing the graph
Some actions tracked by audit log:
- Creating a graph or variant
- Publishing of schema/subschema
- Provisioning or inviting users
- Adjusting billing
- Provisioning or deleting an API key
- Adjustments to settings for schema checks
This is a partial list of what audit logs track, you can see the more complete list of actions tracked in our docs. Audit logs include actions done by individuals as well as automated actions via the API or CLI. Data for the audit log is retained for up to 180 days.
How to download an audit log
Audit logs are accessible by organization admins via a new Audit tab inside Apollo Studio UI. When requesting a log, you can filter your exports to a specific actor, action on a specific graph, and/or specific time window. Once an audit log export is requested you’ll receive an on-screen indication as well as an email notification when the log is ready for download.
Get started Audit logs are part of the Studio Enterprise plan. Please reach out to us if you are interested in this feature.
Stay in our orbit!
Become an Apollo insider and get first access to new features, best practices, and community events. Oh, and no junk mail. Ever.
Make this article better!
Was this post helpful? Have suggestions? Consider so we can improve it for future readers ✨.