Searching Logs
- How to return the week number of the year for a timestamp?
- Why aren't my recent logs showing up with my search?
- The metadata field is not listed in the search query and only showing up in Hidden Fields in the Search UI Browser.
- Are POSIX bracket expressions supported in parse regex?
- I have an aggregate query with aggregation on multiple fields, other charts correctly plot each column as a separate value, the pie chart only displays a single field as 100% of the total. Why is it so?
- Unable to parse input as json
- Receiving error "Multiple definitions found for function formatDate(String, String)" using the formatdate operator. How to resolve it?
- Is there a way to block or allow specific logs from being ingested?
- Is it possible to save a Live Tail search?
- Why does Excel round off an 18 digit numeric value to 15 places in a CSV file generated by scheduled search?
- I enabled the Data Volume Index but there is no information for last month.
- Why is the chart option not available in my search query?
- Can I search my logs on the local cache of my installed collector?
- Why am I receiving error "Lookup table error: File too big"?
- The JSON messages are not being displayed with the JSON view in Sumo Logic UI. Is their any limits on the size of the message in the UI?
- How long is the search query code cached in Sumo Logic?
- Received "You have reached the maximum number of tabs." popup while opening new tab in Sumo Logic UI
- How to search specific timeframes across multiple days?
- What are the supported time periods for the timeslice operator?
- Why is the Auto Complete box no longer showing in the search tab?
- Does Sumo Logic have unique identifer for each ingested log message?
- Metrics query times out with error suggesting "Please consider making the query more selective"
- Percentile (PCT) operation does not generate expected results.
- My scheduled search did not trigger an alert email or webhook
- Error : The following errors were reported when executing your search:<br>Oops! Looks like we encountered a problem. Try running your query again.
- We are not seeing Kubernetes logs in Sumo Logic under the expected sourceCategory
- When parseDate operator processes a null value it generates a "Oops! Looks like we encountered a problem. Try running your query again"
- Display Message Preferences not being saved
- Error in my query while looking up from Threat Intel
- Log showing empty Message field