App Records
This section describes the audit logs that are generated when actions are performed on app records.
Module: "App operation"
Audit logs with the module "App operation" are shown below.
Action: "Record file upload"
This section describes audit logs with the action "Record file upload".
An audit log is generated when:
A file is uploaded to an "Attachment" field.
Level
Information
Information displayed in the "Complement" section
The following information is displayed:
- App ID
- App name
- Record number
- File name
Example of a generated log
app id: *, app name: *, record id: *, filename: *Action: "Record file download"
This section describes audit logs with the action "Record file download".
An audit log is generated when:
One of the following actions is performed on a file attached to a record.
- The file is downloaded
- The file is displayed in an image slide show
Level
Information
Information displayed in the "Complement" section
The following information is displayed:
- App ID
- App name
- Record number
- File name
Example of a generated log
app id: *, app name: *, record id: *, filename: *Action: "Record comment delete"
This section describes audit logs with the action "Record comment delete".
An audit log is generated when:
A comment is deleted.
Level
Information
Information displayed in the "Complement" section
The following information is displayed:
- App ID
- App name
- Record number
- Comment number
Example of a generated log
app id: *, app name: *, record id: *, comment id: *Action: "Record delete"
This section describes audit logs with the action "Record delete".
An audit log is generated when:
A record is deleted.
Level
Information
Information displayed in the "Complement" section
The following information is displayed:
- App ID
- App name
- Record number
Example of a generated log
app id: *, app name: *, record id: [*]Record numbers are separated by commas.
Action: "Record bulk delete"
This section describes audit logs with the action "Record bulk delete".
An audit log is generated when:
Records are deleted in bulk.
Level
Information
Information displayed in the "Complement" section
The following information is displayed:
- App ID
- App name
Example of a generated log
app id: *, app name: *Action: "Record import registered"
This section describes audit logs with the action "Record import registered".
An audit log is generated when:
A file to be imported into an app is registered.
Level
Information
Information displayed in the "Complement" section
The following information is displayed:
- App ID
- App name
- The number of rows in the file
If the user who performs the action sets the first row of the file as the header when importing the file, the number of file rows logged will be 1 less than the actual number of file rows. - File size
- File name
Example of a generated log
app id: *, app name: *, number of file lines: *, file size: *, filename: *Action: "Record import started"
This section describes audit logs with the action "Record import started".
An audit log is generated when:
The operation to import record data from a file is initiated.
Level
Information
Information displayed in the "Complement" section
The following information is displayed:
- App ID
- App name
- The number of rows in the file
If the user who performs the action sets the first row of the file as the header when importing the file, the number of file rows logged will be 1 less than the actual number of file rows. - File size
- File name
Example of a generated log
app id: *, app name: *, number of file lines: *, file size: *, filename: *Action: "Record import finished"
This section describes audit logs with the action "Record import finished".
Any actions performed before the August 2021 update were logged as "Record import".
An audit log is generated when:
The operation to import record data from a file is completed.
Level
Information
Information displayed in the "Complement" section
The following information is displayed:
- App ID
- App name
- The number of rows in the file
If the user who performs the action sets the first row of the file as the header when importing the file, the number of file rows logged will be 1 less than the actual number of file rows. - File size
- File name
Example of a generated log
app id: *, app name: *, number of file lines: *, file size: *, filename: *Action: "Record export"
This section describes audit logs with the action "Record export".
An audit log is generated when:
Record data is exported to a file.
Level
Information
Information displayed in the "Complement" section
The following information is displayed:
- App ID
- App name
Example of a generated log
app id: *, app name: *Action: "Report export"
This section describes audit logs with the action "Report export".
An audit log is generated when:
A graph is exported to a file.
Level
Information
Information displayed in the "Complement" section
The following information is displayed:
- App ID
- App name
Example of a generated log
app id: *, app name: *Action: "Exported file download"
This section describes audit logs with the action "Exported file download".
An audit log is generated when:
A file with record data is downloaded.
Level
Information
Information displayed in the "Complement" section
The following information is displayed:
- App ID
- App name
- File name
Example of a generated log
app id: *, app name: *, filename: *Action: "Webhook notify"
This section describes audit logs with the action "Webhook notify".
An audit log is generated when:
A Webhook notification is sent.
Level
Information
Information displayed in the "Complement" section
The following information is displayed:
- App ID
- App name
- Record number
- Notification ID
- Event type
- Destination server URL
If the notification is successfully sent, the following information is displayed.
- Status code of the notification
If the notification cannot be sent due to an error attributable to kintone, the following information is displayed.
- Error type: CLIENT_ERROR
- Error message
If the notification cannot be sent due to an error attributable to the web service that receives the notification, the following information is displayed.
- Error type: SERVER_ERROR
- HTTP status code of the notification
Examples of generated logs
If the notification is successfully sent
app id: *, app name: *, record id: *, notification id: *, event type: {ADD_RECORD / ADD_RECORD_COMMENT / UPDATE_RECORD / UPDATE_STATUS / DELETE_RECORD}, server url: *, status code: *If the notification cannot be sent due to an error attributable to kintone
app id: *, app name: *, record id: *, notification id: *, event type: {ADD_RECORD / ADD_RECORD_COMMENT / UPDATE_RECORD / UPDATE_STATUS / DELETE_RECORD}, server url: *, error type: CLIENT_ERROR, error message: *If the notification cannot be sent due to an error attributable to the web service that receives the notification
app id: *, app name: *, record id: *, notification id: *, event type: {ADD_RECORD / ADD_RECORD_COMMENT / UPDATE_RECORD / UPDATE_STATUS / DELETE_RECORD}, server url: *, error type: SERVER_ERROR, status code: *Action: "Send slack dm"
This section describes audit logs with the action "Send slack dm".
An audit log is generated when:
A Slack notification is sent.
Level
Information
Information displayed in the "Complement" section
The following information is displayed:
- App ID
- App name
- Record number
- The Slack subdomain to receive the notification
- Login name of the user to whom the notification was sent
- E-mail address of the user to whom the notification was sent
If the notification is successfully sent, the following information is displayed.
- Response status code from Slack API
If the notification cannot be sent due to an error attributable to kintone, the following information is displayed.
- Error type: CLIENT_ERROR
- Error message
If the notification cannot be sent due to an error attributable to the web service that receives the notification, the following information is displayed.
- Error type: SERVER_ERROR
- Response status code from the failed Slack API
- Error message
Examples of generated logs
If the notification is successfully sent
app id: *, app name: *, record id: *, slack subdomain: *, user: *, Email: *, status code: *If the notification cannot be sent due to an error attributable to kintone
app id: *, app name: *, record id: *, slack subdomain: *, user: *, Email: *, error type: CLIENT_ERROR, error message: *If the notification cannot be sent due to an error attributable to the web service that receives the notification
app id: *, app name: *, record id: *, slack subdomain: *, user: *, Email: *, error type: SERVER_ERROR, status code: *, error message: *Properties
The properties displayed in the Complement section of the audit log details are as follows.
"app id"
Indicates app IDs.
"app name"
Indicates app names.
"comment id"
Indicates record comment numbers.
"Email"
Indicates e-mail addresses.
"error message"
Indicates error messages.
"error type"
Indicates error types. The following error types are displayed.
- CLIENT_ERROR: Indicates that the action failed due to an error attributable to kintone.
- SERVER_ERROR: Indicates that the action failed due to an error attributable to the web service that receives the notification.
"event type"
Indicates event types. The following event types are displayed.
- ADD_RECORD: Indicates that a record was added.
- ADD_RECORD_COMMENT: Indicates that a comment was posted.
- UPDATE_RECORD: Indicates that a record was changed.
- UPDATE_STATUS: Indicates that a process management status was changed.
- DELETE_RECORD: Indicates that a record was deleted.
"file size"
Indicates file size.
"filename"
Indicates file names.
"login name"
Indicates the login names of guest users.
"notification id"
Indicates notification IDs.
"number of file lines"
Indicated the number of rows in the relevant file.
"record id"
Indicates record numbers.
"server url"
Indicates server URLs.
"slack subdomain"
Indicates the Slack subdomain to receive a notification.
"status code"
Indicates status codes.
"user"
Indicates login names.