LogoLogo
3.4.3
3.4.3
  • Introduction
  • Getting started
    • Installation
      • On-premises
        • Single-node
        • Multi-node
      • Azure Market Place
      • AWS Market Place
    • Introduction
      • Reports
      • Services
    • Tutorials
      • Amazon AWS CUR
      • Amazon AWS CUR (Athena)
      • Azure Stack
      • Azure EA
      • Azure CSP
      • Google Cloud
      • VMware vCloud
      • VMware vCenter
    • Releases
      • Upgrading to version 3
      • Known issues
      • Archive
  • Reports
    • Accounts
    • Services
    • Instances
    • Summary
    • Budget
  • Services
    • Manage
    • Rates
    • Adjustments
    • Subscriptions
  • ACCOUNTS
    • Budget management
  • Data pipelines
    • Extract
      • Configuration
      • Templates
      • Script basics
      • Parslets
      • Subroutines
        • check_dateformat
        • check_dateargument
        • format_date
        • validate_response
      • Language
        • aws_sign_string
        • basename
        • buffer
        • csv
        • clear
        • discard
        • encode
        • encrypt
        • environment
        • escape
        • exit_loop
        • foreach
        • generate_jwt
        • get_last_day_of
        • gosub
        • gunzip
        • hash
        • http
        • if
        • json
        • loglevel
        • loop
        • match
        • pause
        • print
        • return
        • save
        • set
        • subroutine
        • terminate
        • unzip
        • uri
        • var
    • Transform
      • Transform Preview
      • Configuration
      • Language
        • aggregate
        • append
        • calculate
        • capitalise
        • convert
        • copy
        • correlate
        • create
        • default
        • delete
        • environment
        • event_to_usage
        • export
        • finish
        • if
        • import
        • include
        • lowercase
        • normalise
        • option
        • rename
        • replace
        • round
        • service
        • services
        • set
        • split
        • terminate
        • timecolumns
        • timerender
        • timestamp
        • update_service
        • uppercase
        • var
        • where
    • Datasets
    • Lookups
    • Metadata
    • Reports
    • Workflows
  • Administration
    • User management
      • SAML2/LDAP
      • Users
      • Groups
    • Settings
      • Global Variables
  • Advanced
    • Integrate
      • GUI automation
        • Examples
      • API docs
      • Single sign-on
        • Azure-AD
        • Auth0
        • OneLogin
        • ADFS
        • LDAP
    • Security
    • Digging deeper
      • Authentication flows
      • Transformer datadate
      • Dataset lifecycle
      • Directories
      • Databases
  • Terms & Conditions
  • Privacy Policy
Powered by GitBook
On this page
  • Creating Lookups
  • Importing Lookups
  • Using Lookup file in a Transformer

Was this helpful?

Export as PDF
  1. Data pipelines

Lookups

Lookup files can be imported and created in the Lookups management screen, under data pipelines

PreviousDatasetsNextMetadata

Last updated 5 years ago

Was this helpful?

In certain scenario's it might be required to maintain a statis Lookup file in Exivity. For example, when no logical mapping can be done from certain cloud resources such as mapping of VMware datastores, Azure Resource Groups, T-Shirt Size / Flavor VM's, etc. To apply business logic such as Disk Tiering or Customer identifications, a static Lookup file can be a useful tool to close this gap in your data feed. In this chapter, we explain how to create, import and use a Lookup file in Exivity.

Creating Lookups

To create a new Lookup file, browse to the Data Pipelines > Metadata menu and then click the Create Lookup. To create a new empty Lookup, provide a name and specificy the amount of columns and rows that you'll need (don't worry - you can add/remove columns and rows later):

After clicking the Create button an Excel-like grid will be shown. The first row of the lookup is considered the header which is mandatory. All rows afterwards are values that can be filled in according to your use case. In this example, we're creating a static mapping for VMware Datastores, where each Datastore relates to a specific Department:

In case you want to remove or add a column/row: by right-clicking anywhere in the grid a pop-up will be shown from where you can chose to add/remove a column/row:

When you are finished, click the Update button.

NOTE: make sure there are no empty rows at the end of your lookup file. Failing to do so may cause an import error when using the Lookup in a Transformer

Importing Lookups

In case you already have a Lookup file which you have created elsewhere (i.e. Excel sheet, or CSV export from a CMDB), Exivity offers you the ability to create a Lookup by importing that file.

To import a CSV or Excel sheet as a Lookup file, browse to the Data Pipelines > Metadata menu and then click the Create Lookup. Now click the Import button in the area of the screen which is labelled as Use existing. Now it is possible to make some final changes to your file. Once finished, press the Update button to save your changes.

NOTE: make sure there are no empty rows at the end of your lookup file. Failing to do so may cause an import error when using the Lookup in a Transformer

Using Lookup file in a Transformer

To obtain this path, first open the Lookup using the Lookups menu. Then click the Copy icon to the right of the FILENAME:

Once a Lookup is created, it is possible to import it in a as a for correlating datasets and other use cases. Before opening your Transformer, the first thing to do is obtaining the correct Lookup file path for importing.

Once this has been done, now open your Transformer, and past the path of your Lookup as part of an statement:

DSET
import
Creating a new Lookup
Adding values to a lookup file
Adding and removing columns and rows
Copy Lookup path
Importing a statis Lookup in a Transformer
Transformer