Overview of Resmo resources.

Resources are entities in integration tools. They are created, updated or deleted, meaning they have "changes". Sample resources are Amazon EC2 instances, Amazon S3 buckets, GitHub Repositories or Slack users.

Asset and resource keywords are used interchangeably. Resmo collects a resource's configuration, not the data itself.

For example, an Amazon EC2 instance has a resource like this in Resmo:


Resource Anatomy

Each resource has an associated key and configuration data:

  • Key

    • ie. GitHub has repositories or users which you can access using github_repository and github_user keys in Resmo.

    • Keys are singular.

    • Keys follow the integration key + service name + entity name standard. ie. aws_s3_bucket. If the integration is the service itself, it becomes integration name + entity name. ie. github_repository or slack_channel.

  • Configuration data - in JSON format

    • See the EC2 example above.

Each resource has also changes and they are also available to query. See Resource Changes

Resource Collection

Resources are collected via integrations. Integrations offer different collection methods. Check out the Integrations Guide for more information.

Resource Fields

Each resource has meta object for Resmo related data. At the same level as meta, we write the actual resource object.

Resources have the following field structure:

_meta: {
  event: { -> event's 
    "actor": Any, -> can be a username or an object, depending on the integration
     "type": "renamed",
     "payload": Any -> event's payload
  integration: {
    "id": "",
     "name": "",
     "tags": ["",""]
  resource: "github_repo",
  recordedAt: date,
... -> the rest is resource's content

All Collected Resources

Resmo has more than 200 resources collected in near-real-time and the number is increasing every day. If you want to see all of them take a look at TBA.

Last updated