Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Enable the JSON parser in vRealize Log Insight 4.6 and later (57223)

Last Updated: 11/23/2018Categories: InformationalTotal Views: 3356Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Purpose

Enable the JSON parser in vRealize Log Insight agents to parse JSON objects (key/value pairs) into corresponding event fields.

Impact / Risks

Extremely large JSON messages could result in server side performance issues.
Tested up to ~500 JSON events without issue, when cluster appropriately sized.

Resolution

Windows Agent

Stop the Log Insight agent from the command prompt:

net stop LogInsightAgentService

In the Windows guest, navigate to Control Panel > System > Advanced system settings > Environmental Variables > System Variables and click New to create a new System Variable with the following configuration:

Variable name: STRATA_AGENT_JSONPARSER_FEATURE
Value: 1

Restart the agent from the command prompt:

net start LogInsightAgentService

Linux Agent

In the Linux guest, stop the Log Insight agent:

service liagentd stop

Open /etc/init.d/liagentd in a text editor.

Search for the following line:

# Unknown status almost always indicates that the process exists but the pid file is missing

Below the else clause, add the following line:

export STRATA_AGENT_JSONPARSER_FEATURE=1 # SHOULD BE ADDED BY THE USER TO BE ABLE TO USE JSON PARSER

Example:
# Unknown status almost always indicates that the process exists but the pid file is missing
if [ "$status_code" = "$ERRORCODE_IS_RUNNING" ] || [ "$status_code" = "$ERRORCODE_STATUS_UNKNOWN" ]; then
RETVAL=0
echo -n "Already started."
else
export STRATA_AGENT_JSONPARSER_FEATURE=1 # SHOULD BE ADDED BY THE USER TO BE ABLE TO USE JSON PARSER
$start_daemon $BinaryPath $StartCommand $*
RETVAL=$?

Save and close the file.

Restart the agent:

service liagent restart

Agent Group Configuration

Log into the vRealize Log Insight UI as local admin.

Navigate to Administration > Management > Agents.

Expand the groups and click NEW GROUP to create a new group for agents that will use the JSON parser.

Click Edit to add the following configuration:

[filelog|json_logs_section]
directory=/tmp/test
include=*.log
parser=json

Note: Edit the directory and include values as needed.

Click SAVE NEW GROUP to save the agent group configuration.

Identified JSON objects will be automatically parsed into corresponding event fields key/value pairs and represented as event fields in vRealize Log Insight.

Note: After upgrading LI Agents to 4.6.x and 4.7.x, the JSON parser becomes disabled and will need to be re-enabled.

Related Information

Example JSON:
{  "firstName": "John",  "lastName": "Smith",  "isAlive": true,  "age": 27,  "address": {  "streetAddress": "380 Interlocken Blvd",  "city": "Broomfield",  "state": "CO",  "postalCode": "80021"  },  "phoneNumbers": [  {  "type": "home",  "number": "1 (877) 486-9273"  },  {  "type": "office",  "number": "(303) 942-4600"  },  {  "type": "mobile",  "number": "123 456-7890"  }  ],  "children": [],  "spouse": null  }

Example event field results:
firstname
lastname
isalive
age
address_streetaddress address_city address_state address_postalcode
phonenumbers0_type phonenumbers0_number
phonenumbers1_type phonenumbers1_number
phonenumbers2_type phonenumbers2_number
spouse

Example Interactive Analytics:

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vRealize Log Insight

Related Versions:

VMware vRealize Log Insight 4.7.x

VMware vRealize Log Insight 4.6.x

Take Our Survey

Support Assistant