Processing Ajax...

View Message
Close Dialog

Test Status Rules
Close Dialog

Combined Attachment Content
Close Dialog



Parsed Message Text
Close Dialog



Forward Message
Close Dialog

Separate email addresses with commas or semicolons.

Title
Close Dialog

Message

Confirm
Close Dialog

Confirm
Close Dialog

Confirm
Close Dialog

New Ticketing System: Freshdesk

November 19, 2021

We're pleased to announce that we've added Freshdesk as an external ticketing system for your CheckCentral notifications! To get started with it, login to your CheckCentral dashboard, then click Notifications > External Ticketing Systems. From there you can add it as a new channel and detailed instructions are in the configuration window.

Freshdesk External Ticketing Configuration
Freshdesk External Ticketing Configuration

As always, if you have any questions, please feel free to contact us for assistance!

New Ticketing System: Atera

November 18, 2021

We're pleased to announce that we've added Atera as an external ticketing system for your CheckCentral notifications! To get started with it, login to your CheckCentral dashboard, then click Notifications > External Ticketing Systems. From there you can add it as a new channel and detailed instructions are in the configuration window.

Atera External Ticketing Configuration
Atera External Ticketing Configuration

As always, if you have any questions, please feel free to contact us for assistance!

New Ticketing System: Autotask

November 18, 2021

We're pleased to announce that we've added Autotask as an external ticketing system for your CheckCentral notifications! To get started with it, login to your CheckCentral dashboard, then click Notifications > External Ticketing Systems. From there you can add it as a new channel and detailed instructions are in the configuration window.

Autotask External Ticketing Configuration
Autotask External Ticketing Configuration

As always, if you have any questions, please feel free to contact us for assistance!

New Ticketing System: HaloPSA

November 15, 2021

We're pleased to announce that we've added HaloPSA as an external ticketing system for your CheckCentral notifications! To get started with it, login to your CheckCentral dashboard, then click Notifications > External Ticketing Systems. From there you can add it as a new channel and detailed instructions are in the configuration window.

HaloPSA External Ticketing Configuration
HaloPSA External Ticketing Configuration

As always, if you have any questions, please feel free to contact us for assistance!

Scheduled Reporting Added!

October 4, 2021

CheckCentral is happy to announce that scheduled reporting is here! You can find this new feature under your Notifications menu then the Reports menu item.

What is Scheduled Reporting?

Scheduled reporting is an exciting new feature that allows you to create automated reports for any of your CheckCentral data. Schedule different types of reports to send the data you need to the people that need it, even people outside of your organization.

Navigating to the Daily Digest.
Navigating to the Daily Digest.

You can now manage your Daily Digest report and create new reports that your organization needs in this new reports area.

New CheckCentral reports area.
New CheckCentral reports area.

As always, if you run into any trouble at all, please don't hesitate to contact us.

CheckCentral API Documentation: createReport Endpoint

August 23, 2021

The CheckCentral API provides an endpoint for adding reports programmatically. All of the configuration options are available through the API, detailed below. To add a new report through the API, you will require an API token for your organization with Read/Write access. Organization administrators can create tokens through the API portal on your dashboard.

The endpoint is located at https://api.checkcentral.cc/createReport/?apiToken=APITOKEN where the APITOKEN placeholder is replaced with your valid token. The request must be made with the Content-Type header set to application/json. The body of the request should contain the properties below to configure the new report's settings. Any properties not passed will be set to their default value.

For example, to add a new report you could send the following json in the body of the request:

Code

{
  "name": "Some Report",
  "email": "person@myorg.realdomain",
  "accessLevel": "User",
  "sendWelcomeEmail": true,
  "userGroups": [
    "userGroupID"
  ],
  "notifications": [
    { 
        "type": "failures",
        "services": [
            "sms",
            "push"
        ]
    }
  ]
}

The report data must include a name property as well as any data required to generate the report such as check group IDs or dashboard IDs.

The complete list of possible properties for report creation are as follows:

Report Structure

Parameter Type/Allowed Values Default

name

The name of the new report.

The name parameter is required.

String

report_type

The type of the new report.

The report_type parameter is required.

One of:

  • dashboard
  • checkgroup
  • check
  • activity
  • stats
  • digest

description

A text description of the report. The description will be included in the body of emails delivering the report.

String/td>

source

The name for the new user.

String

format

The output format for the report. Different report sources allow for different formats.

One of:

  • html
  • pdf
  • csv (activity and stats only)
For digest reports, the format will always be set to embedded.

filename

Set an optional filename to use for the report. Reports will be generated with a default filename that includes the date of the report and information such as the report type and content.

String

content

Pass a json object to configure what content CheckCentral will include in the report.

ReportContent {}

ReportContent

Parameter Type/Allowed Values Default

check

Pass a check ID to to use for the report. The check parameter is valid for activity, check, and stats reports. Only one of check and checkgroup may be configured for activity and stats reports.

String

The check parameter is required for check reports.

checkgroup

Pass a checkgroup ID to use for the report. The checkgroup parameter is valid for activity, check group, and stats reports. Only one of check and checkgroup may be configured for activity and stats reports.

String

[]
First Page
Previous Page
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
Next Page
Last Page