Loading

Tines Integration

<div class="condensed-table">
| | |
| --- | --- |
| Version | 1.14.1 (View all) |
| Compatible Kibana version(s) | 8.14.0 or higher |
| Supported Serverless project types
What’s this? | Security
Observability |
| Subscription level
What’s this? | Basic |
| Level of support
What’s this? | Community |

</div>
Tines makes data, including logs, related to use and configuration of a Tines tenant available via a REST API.

This integration can be used to collect:

  1. audit logs
  2. time saved reports

The Tines API documentation is available via this page.

The package collects "audit log" events and "time saved" reports from the Tines API.

At present the only API version available, and hence the version assumed to be polled by this integration, is v1.

The audit logs list endpoint is documented here.

The time saved reporting endpoint is documented here.

This is available within the Tines web interface via the URL bar, e.g. https://your-tenant-1234.tines.com

Note

the trailing domain may be tines.io for your particular tenant.

Refer to this documentation from Tines regarding how to create an API key.

The API key can be either a Personal or Tenant API key.

  1. In Kibana go to Management > Integrations
  2. In "Search for integrations" search bar type Tines
  3. Click on "Tines" integration from the search results.
  4. Click on Add Tines button to add the Tines integration.
  5. Modify the Tines Tenant URL as appropriate
  6. Insert your Tines API user email address
  7. Insert the Tines API key created associated with the API user email address
Example Integration Configuration

There are two dashboards immediately available as part of the integration.

The Tines Audit Logs summary dashboard,

Tines Audit Logs

And the Tines Time Saved dashboard,

Tines Time Saved

All fields ingested to this data stream are stored under tines.audit_log as each audit_log event is stored individually.

All fields ingested to this data stream are stored under tines.time_saved as each time saved report event is stored individually.