API Log in DomoStats


We want to do an audit of datasets accessed via API calls, as well as the clients using those calls, and I was amazed that this isn't logged as part of DomoStats (or the deprecated (?) Domo Governance datasets). I am recommending that this be added either through DomoStats or some other mechanism.
Comments
-
What is the purpose of the Activity Log if it does not include ALL activity! If It rely on just the activity log to decide if a data set is no longer needed, then it has the distinct possibility of breaking API calls.
1 -
Hi, @jimsteph - the Activity Log report in DomoStats includes a column "Client_ID", which gives the client ID of the API client used in performing the logged activity. Does that give you what you need? (Note: unfortunately, we don't currently have a similar type of information for actions taken using a Domo access token)
0
Categories
- All Categories
- 1.9K Product Ideas
- 1.9K Ideas Exchange
- 1.6K Connect
- 1.3K Connectors
- 305 Workbench
- 6 Cloud Amplifier
- 9 Federated
- 3K Transform
- 107 SQL DataFlows
- 648 Datasets
- 2.2K Magic ETL
- 4K Visualize
- 2.5K Charting
- 775 Beast Mode
- 75 App Studio
- 43 Variables
- 734 Automate
- 186 Apps
- 471 APIs & Domo Developer
- 63 Workflows
- 14 DomoAI
- 40 Predict
- 17 Jupyter Workspaces
- 23 R & Python Tiles
- 403 Distribute
- 117 Domo Everywhere
- 277 Scheduled Reports
- 9 Software Integrations
- 137 Manage
- 134 Governance & Security
- 8 Domo Community Gallery
- 44 Product Releases
- 12 Domo University
- 5.4K Community Forums
- 40 Getting Started
- 30 Community Member Introductions
- 113 Community Announcements
- 4.8K Archive