/alerts/notes - Append an operator note to an alert's timeline

Add MCP server to your AI tool

Allow AI tools and LLMs to interact with the API documentation portal through MCP.

MCP server URL

https://api.my.nethesis.it/mcp

Standard setup for AI tools providing an mcp.json file

mcp.json 
{
  "my.nethesis.it MCP server": {
    "url": "https://api.my.nethesis.it/mcp"
  }
}
Close
POST /alerts/notes
Bearer auth

Appends a free-form operator note (ticket links, findings, hand-over info) to the alert's activity timeline as a note_added event. Notes are independent from silences and assignments, immutable (append-only) and can also target an alert that has already resolved — the timeline outlives the alert, so no Mimir lookup is performed.

Notes are namespaced by organization: they are written under the caller-resolved organization_id and only readable through that organization's timeline.

Requires manage:systems permission on an organization in the caller's hierarchy. Customers are pinned to their own organization.

Query parameters

  • organization_id string

    The alert's organization (its organization_id label). Required for Owner/Distributor/Reseller; ignored for Customer (pinned).

application/json

Body Required

  • fingerprint string Required

    Alertmanager fingerprint of the alert

    Format should match the following pattern: ^[A-Za-z0-9._:-]{1,128}$.

  • text string Required

    Note text (trimmed; must not be blank)

    Maximum length is 2000.

Responses

  • 200 application/json

    Note appended to the timeline

    Hide response attributes Show response attributes object
    • code integer
    • message string
    • data object | null
  • 400 application/json

    Bad request - validation error

    Hide response attributes Show response attributes object
    • code integer

      HTTP error code

    • message string

      Error message

    • data object
      Hide data attributes Show data attributes object
      • type string

        Type of error

        Values are validation_error or external_api_error.

      • errors array[object]
        Hide errors attributes Show errors attributes object
        • key string

          Field name that failed validation

        • message string

          Error code or message

        • value string

          Value that failed validation

      • details

        Additional error details
  • 401 application/json

    Unauthorized - invalid or missing token

    Hide response attributes Show response attributes object
    • code integer
    • message string
    • data object | null
  • 403 application/json

    Forbidden - insufficient permissions

    Hide response attributes Show response attributes object
    • code integer
    • message string
    • data object | null
POST /alerts/notes 
curl \
 --request POST 'https://api.your-domain.com/api/alerts/notes' \
 --header "Authorization: Bearer $ACCESS_TOKEN" \
 --header "Content-Type: application/json" \
 --data '"{\n  \"fingerprint\": \"79b1c79b3211797c\",\n  \"text\": \"Firewall irraggiungibile, sentito il cliente: intervento on-site domattina. Ticket #123\"\n}"'
Request example 
{
  "fingerprint": "79b1c79b3211797c",
  "text": "Firewall irraggiungibile, sentito il cliente: intervento on-site domattina. Ticket #123"
}
Response examples (200) 
{
  "code": 200,
  "message": "alert note added successfully",
  "data": null
}
Response examples (400) 
{
  "code": 400,
  "message": "validation failed",
  "data": {
    "type": "validation_error",
    "errors": [
      {
        "key": "username",
        "message": "required",
        "value": "string"
      }
    ]
  }
}
Response examples (401) 
{
  "code": 401,
  "message": "invalid token",
  "data": {}
}
Response examples (403) 
{
  "code": 403,
  "message": "insufficient permissions",
  "data": {}
}