Audit Log

Audit Log

The Audit Log is a chronological sequence of entries, each resulting from the activities performed by a Profile owned by you. Audit logs determine what has happened before and after an event, and identify records associated with certain events.

You can monitor activities such as the addition and deletion of a Device, changes in Access Management policies, Analysis, and so on.

Only Starter or Scale plans are allowed to filter log entries. Check out our pricing page.
Only the account that owns the profile can visualize the log. The users added as Team Members cannot visualize logs from shared profiles.

Events

Each action executed by an agent on a resource is considered an event. Agents can be, for example, the TagoIO or TagoRUN system, your account, or another team member's account. As for resources, it can be a Device, Analysis, or even an Access Management policy.

TagoIO keeps a 6-month log for each profile, events older than that will not be displayed.

Filtering events

Since the Audit Log is quite exhaustive, it could be tiresome to sift through the entries if you are looking for a few specific details. In such a case, you can use the Filter options offered to you and narrow down on the entry or entries you are looking for.

Timezone

The Audit Log will use your account's timezone preference to show you the timeline of events in ascending order. Choosing a new timezone will change the timeline, filter, and log when downloading it.

Time interval

Find out what has been done on your profile using the Time Interval filter that lets you inspect the events that happened in a determined time range.
Shorter time ranges can make the search faster, also this is limited to a maximum of 7 days.

Event initiator

Look for events executed by a specific agent. It can be you, a team member, a TagoIO system, or a TagoRUN system.
Team members that have been removed will be listed on Audit Log as "Unknown user"

Resource Type

Search for events related to a particular resource type, and show only the events that you are interested in. You can list all events related to Devices, Actions, Analysis, and more.

Resource ID

Look for an Action that has been deleted or a Device that was updated by using the Resource ID filter. The Resource ID filter lets you search for events related to this specific resource.
It's not necessary to type the Resource ID (e. g. profile id, device id) if you select a Resource Type, because the filter will change to a dropdown with a list of all resources ID related.


Event Messages

Each event has a message describing which action was done to the specific resource. For example, when you create a widget, update an Action or one of your Run users.


You can use this option to filter specific events like the one above.


Automation

You can also access the Audit Log using our SDK, Analysis, and Actions to automate processes to back up your log events. If you need further assistance, check out our Community.


Downloading a copy

You can download a copy of the audit log entries in PDF format by clicking on the Download button in the top right corner. Only the listed activities displayed in the feed will be printed out.



    • Related Articles

    • Chunk Management [beta]

      The Chunk Management feature is a powerful tool that allows you to easily manage your data, either to create backups or delete information from your bucket. Chunk Management is only available for Optimized Device Data (Immutable)  By accessing your ...
    • Console for Debug

      Use the console to monitor the variables and status of your script. You can see any error or text generated by “console.log”. This console is a very good debug tool. Console Screen: Any error or response to a “context.log” will show up here; Clear ...
    • Parser vs. Analysis Comparison

      The Payload Parser was created to handle raw payload sent by the devices in order to extract the measured variables or execute simple operations. Analysis is much more powerful, including access to buckets and external services. Also, there is a cost ...
    • SenRa Network

      Using this article, the user will learn how to integrate a LoRaWan device with SenRa Network and Tago.   This setup is for the uplink operation: data sent from the device to your TagoIO account.  The integration is accomplished in two parts: 1) ...
    • Account Token

      The secret key used between Tago and external applications are Account Tokens. Any access from an account will only be granted with a valid token, so it is vital that this token be kept secret and only be shared with those you trust. All sorts of ...

        Take a look at our updated roadmap here!
          What would you like to see on TagoIO?

            Future and past Webinars