LogicMonitor seeks to disrupt AI landscape with $800M strategic investment at $2.4B valuation to revolutionize data centers.

Learn More

    Platform

    Get real-time insights and automation for comprehensive, seamless monitoring with agentless architecture.

  • Infrastructure
    monitoring
  • Cloud monitoring
  • Digital experience
  • AIOPS

      • Solutions

      Whether you work in MSP, Enterprise IT or somewhere in between, the solution is clear.

    By Initiative
    By Industry

      About us

      Get to know LogicMonitor and our team.

    Get to know us
    Services

      Resources

      Explore our blogs, guides, case studies, eBooks, and more actionable insights to enhance your IT monitoring and observability.

    Learn

      Documentation

      Read through our documentation, check out our latest release notes, or submit a ticket to our world-class customer service team.

    Support

    Product Documentation

    Getting EventSource Details

    Last updated on 08 October, 2024

    You can use LogicMonitor REST API v3 to get a list of EventSources. You must authenticate yourself before making the API request.

    Getting List of EventSources

    URI: GET /setting/eventsources

    ParameterTypeDescription
    formatStringThe supported format of API response are JSON and XML. JSON is set as the default format.
    fieldStringThe response is filtered to include only the specified fields for each object. You can provide a list of properties separated by a comma. 
    Example – /setting/eventsources?fields=version
    sizeIntegerIndicates the number of results to display. A maximum of 1000 results can be requested in a GET call. By default, a list of 50 EventSources is returned if a value is not provided for this parameter.
    Example – /setting/eventsources?size=5
    offsetIntegerIndicates the number of results to offset the displayed result. By default, the offset is set to 0.
    Example – /setting/eventsources?offset=2
    filterStringThe response is filtered according to the operator and specified value that is, filter=property:value
    • Use an asterisk (*) to match more than one character
    • Use a dot (.) character to filter values within an object (example – custom properties)
    • Use a comma (,) to separate multiple filters
    Operators include:
    • Greater than or equals: >:
    • Less than or equals: <:
    • Greater than: >
    • Less than: <
    • Does not equal: !:
    • Equals: :
    • Includes: ~
    • Does not include: !~
    Example – /setting/eventsources?filter=version<12
    In This Article