Follow

Renaming the Entities tab in Dashboard

Renaming Entities Tab

This topic will walk you through the steps of renaming the Users and Machine tabs on your Dashboard. The process will involve editing the investigator.yml file.

Step 1 - Edit investigator.yml

Log into the Reporting node and edit /opt/interest/etc/investigator.yml, navigating to the #ui-config section. It should look similar to this:         

#ui-config:

#   Allowed mapping types are 'file', 'machine', 'project', 'server', 'user', 'volume', 'printer', 'share', 'resource', 'website', 'ip'

#   Only mappings that need to be overriden need to be specified. Others will be filled in with interset defaults.

#   Values for plural, singular and query must be at most 12 characters long. Values across mapping types for plural, singular and query must be distinct.

#  <tid>:

#    machine:

#      plural: "Machines"

#      singular: "Machines"

#      query: "machine"

#    user:

#      plural: "Users"

#      singular: "User"

#      query: "user"

#  showExperimental:

#    <tid>: false

 

Step 2  - Modify mapping names

Change the mapping names to the desired name and ensure that the appropriate fields are not commented out.

In this example we will change “Machines” to “Computers” and “Users” to “People”.

Note:  Names of the mappings can only be a maximum of 12 characters long.

ui-config:

#   Allowed mapping types are 'file', 'machine', 'project', 'server', 'user', 'volume', 'printer', 'share', 'resource', 'website', 'ip'

#   Only mappings that need to be overriden need to be specified. Others will be filled in with interset defaults.

#   Values for plural, singular and query must be at most 12 characters long. Values across mapping types for plural, singular and query must be distinct.

 int:

   machine:

     plural: "Computers"

     singular: "Computer"

     query: "computer"

   user:

     plural: "People"

     singular: "People"

     query: "People"

#  showExperimental:

#    <tid>: false

 

Step 3 - Restart Reporting

Save the changes you made to investigator.yml and then restart reporting:

monit -g reporting stop

monit -g reporting start

Notes:

You can check the status of reporting with monit status investigator.

If investigator fails to start, check that all related fields are not commented out and have the correct spacing. Incorrect spacing will prevent reporting from starting. Yml files require 2-space indents.  Monit logs should offer insight into what was misconfigured:

less +F /var/log/monit

Step 4 - View results

Log into your Interset Dashboard. The names of the tabs should now be changed to what was set in investigator.yml. See below for an example of the changes.



Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

Powered by Zendesk