LogicMonitor seeks to disrupt AI landscape with $800M strategic investment at $2.4B valuation to revolutionize data centers.
Learn MoreGet real-time insights and automation for comprehensive, seamless monitoring with agentless architecture.
Whether you work in MSP, Enterprise IT or somewhere in between, the solution is clear.
Get to know LogicMonitor and our team.
Explore our blogs, guides, case studies, eBooks, and more actionable insights to enhance your IT monitoring and observability.
Read through our documentation, check out our latest release notes, or submit a ticket to our world-class customer service team.
Get real-time insights and automation for comprehensive, seamless monitoring with agentless architecture.
Whether you work in MSP, Enterprise IT or somewhere in between, the solution is clear.
Explore our blogs, guides, case studies, eBooks, and more actionable insights to enhance your IT monitoring and observability.
Get to know LogicMonitor and our team.
Read through our documentation, check out our latest release notes, or submit a ticket to our world-class customer service team.
Come join our live training webinar every other Wednesday at 11am PST and hear LogicMonitor experts explain best practices and answer common questions. We understand these are uncertain times, and we are here to help!
Sign up hereYou can use LogicMonitor’s REST API to programmatically get your OpsNotes. With the OpsNotes resource, you can:
As with all of our API calls, authentication is required.
Returns a list of Ops Notes
HTTP Method: GET
URI: /setting/opsnotes
Request Parameters: By default, a list of 50 ops notes will be returned. You can include sort, filter, fields, size and offset parameters in your request to control what data is included in the response and how it is formatted. Note that query parameters are not considered part of the resource path, and should not be included the calculation of the LMv1 authentication signature.
Property |
Syntax |
Description |
Example URI |
| sort | sort={+ or -}property | Sorts the response by the property specified in either increasing (+) or decreasing (-) order | /setting/opsnotes?sort=-id |
| filter | filter=property{operator}value | Filters the response according to the operator and value specified. Note that you can use * to match on more than one character. You can filter on tags, createdBy, happenedOn, monitorObjectGroups, monitorObjectNames, and _all fields, and multiple filters can be separated by a comma.
Operators include:
|
/setting/opsnotes?filter=note~upgrade |
| fields | fields={list of properties separated by commas} | Filters the response to only include the following fields for each object | /setting/opsnotes?fields=note,id |
| size | size=integer | The number of results to display. Max is 1000. | /setting/opsnotes?size=5 |
| offset | offset=integer | The number of results to offset the displayed results by | /setting/opsnotes?offset=2 |
Returns details for a particular ops note
HTTP Method:GET
URI: setting/opsnotes/{id}
Request Parameters: You can include a filter parameter that controls which fields are displayed in the response:
Property |
Syntax |
Description |
Example URI |
| fields | fields={list of properties separated by commas} | Filters the response to only include the following fields for each object | /setting/opsnotes/{id}?fields=note,id |