Loggly is a cloud based tool used to monitor and analyze logs for specific events.
How to Login:
Go to https://my.solarwinds.cloud/home . Enter Username and password. From the left panel, click on Logs and Log Explorer.
The following screen will open up. By default there will be a single tab when you login, you can open multiple tabs to track different events at the same time.
Set the correct date/time range to check for fatal errors, you can select from a set of specific time range options or select custom and give different and dedicated date/time ranges.
In the Search Logs box, search for the keywords relating to the Fatal/Error you want to search the logs for. Always type the keywords in double quotes (“”). To search for a specific region or tenant id, add the same after typing in the keyword in the following format:
“Keyword”+orgid
How to search for specific regions & tags:
To search for specific Regions, or even for specific ips, or any other dedicated information, we can use tags. Tags allow us to highlight specifications needed while searching logs.
For example: To search for fatals in Mumbai region, we can search for “Keyword”+tag:*MUM*.
Always remember to add tags in between two asterisks (*tagname*).
After getting filtered results, you can further add tags which you want to see and which you do not want to see with the use of “+” and “-“symbols.
For example:
If you want to check for Automation Fatals in Ireland region, but do not want to see fatals for v2 rest APIs, you can write the following expression in the search bar:
“Automation_Fatal”+tag*IR*-*Fatal.Rest.v2.Core*
Use of Operators in Search condition:
We can use “AND” and “OR” operators to create complex search queries, which can be further used in monitoring and creating alerts (this access is not available to support team).
An example of using AND and OR operators along with “=” and “-” is as below
How to read Logs:
The event timeline will show you the exact number of events for a specific search/query made. Upon scrolling down you will be able to see all errors/fatals along with further details to drilldown.
We can search for Request data, which will provide us with further details pertaining to lead/opportunity/activity id, depending upon the trigger type.
Further details like activity type, activity code and created by (userid) can also be accessed.
Next we can search for Exception Message to get to know the exact reason for failure/delays. The exception message can then be used to further reference constant 500 errors and failures.
We can search for workflow actions logs using “WFA” keyword, and then further adding relevant necessary tags.
To check where the automation/action failed/got stuck we can also check for currentaction, which can store information like if else card/distribution card or any other workflow cards for that matter.
