API Programming Guide › API Troubleshooting

Previous Topic: Embed Content in a Liferay Portal

Next Topic: Common Event Grammar

API Troubleshooting

If your API calls are not working as you expect, take the following steps to troubleshoot, testing after each to see if the appropriate results appear.

  1. Verify the URL call syntax:
    1. Compare your syntax to the example in the guide, verifying that you have used your own correct CA Enterprise Log Manager server name or IP address.
    2. If you have added query or report specifications, check that the main part of the call (before the specification parameters) ends with the question mark (?) character, before any parameters are added. For example: 
      ?param1=val1&param2=val2
  2. If the URL syntax is correct, and no data appears, verify the filters. If you are using getQueryViewer or getReport Viewer, review the filters and result condition settings in the interface. If you are using runQuery, review the parameter specifications you added to the URL:
    1. Check Filters - Verify that the base filters show the data you want. For example, the event source name you are filtering is entered correctly.
    2. Syntax - Verify that the filter syntax is correct, especially if you have constructed filters using specification parameters.
    3. Time Filters - Verify that your time range is broad enough, and that the timezone of your operating system is same as the timezone of CA Enterprise Log Manager.
    4. Access Filter XML filter - Verify that you log out of a session successfully.
    5. LogDepot log - Verify that events are being received, and appear in the logDepot_sponsor.log file.
  3. Review the logging settings for the API component. Verify that the following files and settings are in place: