Jeff8682

Members
  • Content Count

    3
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Jeff8682

  • Rank
    Community Member
  1. Blake, If I understand you correctly, I think you are talking about something similar to what we do on status hub not status page but I think you could handle it with a similar process. We have our different products with multiple services under each sometimes. These services are all updated independently by creating the generic webhook integration in statushub. We then create a property on the webcheck or device - statushub.token=#######. When an alert is triggered it posts to the webhook and appends the token that references the service in status hub. payload={ "title": "This service is currently experiencing issues and we are investigating.", "message": "We apologize for the inconvenience!", "type": "investigating", "status": "down", "service_token": "##statushub.token2##" } This should work pretty much the same way using the component api that they offer when I took a quick glance at their docs. You would just append the token in the API component Url that you use to post. Maybe this will help you or at least give you an idea of how you could solve it...
  2. See the integration's description for the property that will need to be added to the devices/websites that you want to post alerts for to statushub. { "enabledStatus": [ "active", "clear" ], "parseMethod": "", "name": "statushub-via-payload", "ack": null, "clear": { "headers": [], "password": "********", "method": "post", "payload": "payload={\n \"title\": \"This service has returned to normal.\",\n \"message\": \"Service: ##WEBSITE##; Service Description: ##WEBSITEDESCRIPTION##\",\n \"type\": \"resolved\",\n \"status\": \"up\",\n \"service_token\": \"##statushub.token##\"\n}", "payloadFormat": "formdata", "url": "https://hooks.statushub.io/hooks/generic_hook", "username": "" }, "description": "INTERNAL ONLY - More detailed\nUP / DOWN\nService token in payload instead of url, means one integration instead of an integration per service.\nproperty: statushub.token", "active": { "headers": [], "password": "********", "method": "post", "payload": "payload={\n \"title\": \"This service is currently experiencing problems\",\n \"message\": \"Service: ##WEBSITE##; service.description: ##WEBSITEDESCRIPTION##\",\n \"type\": \"investigating\",\n \"status\": \"down\",\n \"service_token\": \"##statushub.token##\"\n}", "payloadFormat": "formdata", "url": "https://hooks.statushub.io/hooks/generic_hook", "username": "" }, "update": null, "type": "http", "parseExpression": "", "uiDetails": "{\"includeIDInHttpResponse\":false,\"groupInfo\":[[\"active\",\"clear\"],[\"active\"]],\"multipleMode\":true}" }
  3. Irievibe, This is what we use for integrating with our on-prem Jira instance. Should just need to update the things I blanked out with ### and the correct "field ID's" for your setup and import it. Should give you a starting point if nothing else. { "enabledStatus": [ "active", "update", "clear" ], "parseMethod": "jsonPath", "name": "jira-###", "ack": null, "clear": { "headers": [], "password": "********", "method": "post", "payload": "{\n \"update\": {\n \"comment\": [\n {\n \"add\": {\n \"body\": \"Alert cleared, auto-closing ticket.\"\n }\n }\n ]\n },\n \"transition\": {\n \"id\": \"171\"\n }\n}", "payloadFormat": "json", "url": "https://jira.####.com/rest/api/2/issue/##EXTERNALTICKETID##/transitions", "username": "###service_account###" }, "description": "integration to generate tickets for alerts for ###", "active": { "headers": [], "password": "********", "method": "post", "payload": "{\n \"fields\":{\n \"project\":\n {\n \"key\": \"HOST\"\n },\n \"summary\": \"##LEVEL## - ##HOST####WEBSITE## - ##INSTANCE##\",\n \"description\": \"##HOST####WEBSITE##\\nDatasource: ##DATASOURCE##\\nDatapoint: ##DATAPOINT##\\nLevel: ##LEVEL##\\nStart: ##START##\\nDuration: ##DURATION##\\nThreshold: ##THRESHOLD##\\nValue: ##VALUE##\\nURL: ##URL##\\nAlert URL: ##AlertDetailURL##\",\n \"customfield_17567\": {\n \"self\": \"https://jira.#####.com/rest/api/2/customFieldOption/22162\",\n \"value\": \"Medium - Inconvenienced\",\n \"id\": \"22162\"\n },\n \"customfield_17568\": {\n \"self\": \"https://jira.#####.com/rest/api/2/customFieldOption/30804\",\n \"value\": \"Automated Alert\",\n \"id\": \"30804\"\n },\n \"customfield_18861\": [\n {\n \"value\": \"####\"\n }\n ],\n \"issuetype\": {\n \"name\": \"Request\"\n }\n }\n}", "payloadFormat": "json", "url": "https://jira.####.com/rest/api/2/issue", "username": "###service_account###" }, "update": { "headers": [], "password": "********", "method": "post", "payload": "{\n \"body\": \"Logic Monitor event is now at severity level: ##LEVEL##\"\n}", "payloadFormat": "json", "url": "https://jira.####.com/rest/api/2/issue/##EXTERNALTICKETID##/comment", "username": "###service_account###" }, "type": "http", "parseExpression": "key", "uiDetails": "{\"includeIDInHttpResponse\":true,\"groupInfo\":[[\"update\"],[\"clear\"],[\"active\"]],\"multipleMode\":true}" }