Chuck is correct - if you look at the job menu where you executed the job manually, there'll be a related list at the bottom of that for Job Logs - click on the entry for the log with the warnings you'd like to see, and it will open a new record - the related list in that record will show you every line that the logs wrote. To jump to only errors and warnings, right click on the word "Information" for any of them that show "Information" and choose "Filter Out" - the ones that are left will be the important ones.
The most common warnings that you'll see revolve around the number of records that we collect for a given indicator - 5000 by default. So if you complete more than 5000 incidents in a day, for example, or have more than 5000 incidents open on a day, you'll get a warning when that data is collected that warns you "More than 5000 records exists for this Indicator, we're keeping only the first 5000". It's not anything to be concerned about, just for your awareness of what's happening. It won't stop collections, and the count will still be accurate, only when you drill into the "Records" section of the Scorecards, it will only show the first 5000. There's not a lot you can do about these warnings. You can probably reasonably raise that limit to 10,000 in the Performance Analytics properties if you're consistently at 6k or so, but I would only do that if your intent is to use that records list to take specific action. If you just want an understanding of some of the reasons those records meet the criteria, 5,000 records is a pretty substantial sample size, and most customers aren't going to look at each of the 5,000 records specifically, much less ask for more. So I wouldn't raise the limit only to get rid of this type of warning - I would just check periodically to make sure those are the only warnings you're getting.
Another common warning is when you're collecting a breakdown matrix, or second level breakdowns. There is a limit to the number of 'pairs' that it will collect for, so if you're collecting things like "Priority" for "State", then that's no problem. "Priority" per "Assignment Group" is usually fine as well - but something like "Manufacturer" by "Vendor" for some of the CI ones, for example, usually causes so many breakdown pairs that it won't collect them, and just warns you. To prevent those warnings you can add the offending breakdowns to the Breakdown Matrix exclusions - but it's also worth asking if you need a breakdown matrix at all, or if regular breakdowns are good enough for what you're trying to do. Breakdown matrixes cause an exponential load on the system, and disabling any you don't need will speed up your jobs quite a bit.
Hope the information helps!
