Update OpsNotes
Last updated on 29 June, 2022You can use LogicMonitor’s REST API to update the Ops Notes in your account.
As with all of our API calls, authentication is required.
HTTP Method: PUT
URI: /setting/opsnotes/{id}
Request Parameters:
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 update the Ops Notes in your account.
As with all of our API calls, authentication is required.
HTTP Method: PUT
URI: /setting/opsnotes/{id}
Request Parameters:
Property |
Description |
Required? |
Type |
Example |
note | The note message | Yes | String | “note”:”software update from 1.0.0 to 1.2.4″ |
happenedOnInSec | The date and time associated with the note, in epoch seconds format | No. Defaults to current time | Integer | “happenOnInSec”:1488826440 |
scopes | The scopes associated with the note. A note with no scope will show up for everything in the account. Each scope object should have a type (device, service, deviceGroup, serviceGroup). For group scopes, a groupId should be specified. For device/service scopes, deviceId/serviceId should be specified & groupId can optionally be included. | No. Defaults to no scope | JSON Object | “scopes”:[{“type”:”device”,”deviceId”:56},{“type”:”service”,”serviceId”:87,”groupId”:74}] |
tags | The tags that should be associated with the note. Each tag has a unique id and a name – you can either include the name of a new or existing tag, or the id of an existing tag. | No. Defaults to no tags | JSON Object | “tags”:[{“name”:”release”},{“name”:”upgrade”}] |