Knowledge Base

How To Articles

Custom Types are useful for converting plain text from an E-Mail or Webhook into something useful like a status.

Here is a short video if  you'd prefer to see it in action: 

https://vimeo.com/765511104/32a541880d

Under Custom Types for example we have a default field of Status: 

So for example if I want to convert Email or Webhook text to a status you can simply add the natural language that would come from that email or webhook into the appropriate category such as Error status shown to the right on the screenshot. 

Then lets say I want to pick up some text in an email that has the word Fail in it I can change the type to Status and the system will then show that as a failure when we process the email.

You can use the parsing system to select the text that you want to key on in the email and set the identification parameters. 

 

Normal parsing of text would extract the text as you selected it using the "Text" field option

Once you click confirm you can change the field you created to a "Status" field. Shown below is how we converted the natural word "failed" to an "Error" Status. 



 

 

Meraki portal doesn't allow users to update alerting settings on more than one network at a time. Alert Manger allows you to apply templates to more than one org and network at the same time. This allows an MSP or Enterprise to standardize their alerting settings very quickly across one or all orgs. 

Alert Manager also leverages Webhook technology to monitor real time alerts from Meraki as events happen. This template technology allows you to set the webhook settings to get those alerts to Alert Manager quickly so we can help you reduce the noise in your ticketing system. 

First generate a webhook in Alert Manager by clicking on Data Sources -> Webhooks: 

Click on Get, Then select Cisco Meraki and Basic Template. Then copy the webhook URL as you will paste that into the template in a future step. 

Give the Webhook a Name, Select the ID fields as shown below. Change Alert Type to "Status" and click Submit. 

 


Click Link to Webhook and Select Create. 



 

 

 

Now go to Integrations -> Alert Templates. This will add the Alert Manager webhook as an option to use the in Alert settings below.

Click on General Alert settings next and click the + as shown below under Alert Hooks section. 

Select the Webhook name you gave it above: 

Then select the behavior you want. There are two options one is for Email behavior, and one is for Hooks (webhooks) behavior. Overwrite will overwrite all settings in that category. Append will append the settings to existing ones and skip will not take any action. 

 

Next Click Alerts and select an alert such as Gateway goes offline. Click Enable and then change the time to 5 min or whatever time frame you'd like to be alerted when something goes offline. 

IMPORTANT NOTE: You do not need to select Webhooks or Emails here as these are only for if you want something additional to what you already set globally in the above steps. For example when something goes offline you may want an email to go to someone in addition to the webhooks that happen. 

 

Be sure your template has a name and click Submit. 

Now you can apply the template to one or more Orgs by following the wizard after selecting the page icon. 

The system will then apply the template to whatever orgs/networks you selected. Once they are applied you can see inbound webhooks that come from Meraki to Alert Manager by clicking on Data Sources -> Webhooks and clicking on the eye icon to the right. 

Alert Integration Setup

Login to your Meraki and click on your email address in the top right and select My Profile.

 

Scroll down until you see Generate API option. The API key you generate will only allow Alert Manage to access the organizations that you have access to view. 

 

Copy your API key, you will need to paste this into Alert Manager per the steps below: 

Check to ensure Dashboard API access is enabled. Click on Organization and then settings. 

Then check the box showing dashboard access: 




Login to Alert Manager  and Click on Integrations -> Alert Integrations. Click Add New

Click on Meraki

Give the integration a name and copy the API key from the first step. Click Setup. 

Sign into your Halo PSA system and click on Configuration and then Integrations 

Find and copy the resource server link without the /api part. Then click on View Applications. 

Click on New
 Give it an application Name, we recommend Alert Manager. Select Client ID and Secret then click on Generate. Copy the Client ID and Client Secret to Alert Manager along with your URL from the previous step. Set the Login type to Agent and select a user with appropriate permissions. 


 

Click on Permissions

Select the following permissions: 

Click Save

General Support

The first thing you'll need to do is create a mailbox when you login the first time. You can manually forward emails or utilize rules in Outlook or filters in Gmail to forward emails to the system automatically. Alternatively if have other software that can send emails directly you can set those up to send directly to the new email created. 

Here are three helpful articles to show you how to forward from Gmail and Office 365/Outlook. 

Automatically forward Gmail messages to another account - Gmail Help (google.com)

Turn on or off automatic forwarding in Outlook.com

Use rules to automatically forward messages (microsoft.com)

You can click on the copy icon next to the mailbox to copy the email address you just created. 

 Once you send in some emails click on Documents

 

Then click into the document subject to begin setting up the parsing rules. 

 

General Support

To setup a connection from Alert Manager to Zapier open up Alert Manager and generate an API key under Settings -> API Keys. Then click Add. 

Give it a name and set the appropriate expiration period, then click Confirm. 

Click on Copy for the key: 

Now login to your Zapier account or create a new account on https://www.zapier.com

Click on My Apps, Then click on Add Connection as shown below: 

Search for "AlertManager" and click on Connect and then utilize your API key to connect. 

Once you have the app connected you can target any data view you created from the email parser setup and the system can automatically parse/update data in 4500+ Zapier apps. 

General Support

Create application in your Slack account

To connect your alerts via Notifications to Slack please follow the instructions below:

  • Create new Application using menu “From an app manifest”

  • Select your workspace
  • Insert custom yaml into the form
 <div>
  <img src="https://app.alertmanager.io/static/media/copyGrey.7d9bc2cf.svg" alt="iconCopy" style="top: 0px; right: 0px; margin: 1rem; position: absolute;">
  <code>_metadata: major_version: 1 minor_version: 1 display_information: name: AlertManagerApp features: bot_user: display_name: AlertManagerApp always_online: false oauth_config: scopes: bot: - incoming-webhook settings: org_deploy_enabled: false socket_mode_enabled: false token_rotation_enabled: false
  • Install your App into workspace and allow to send messages to a certain channel

  • Get the web hook Url

  • Open Notifications - Slack settings and put web hook Url here
  • Test the hook url (you have to see the green result and the message in your slack channel).

Create MS Teams integration

To add a possibility to send messages to a MS Teams you need to do the following:

  • Open MS Teams application and required channel

  • Open channel connections

  • Find Incoming Webhook connection. Add and configure it

     

    • Provide name, image and press "create"

     

    • get the Webhook URL

     

  • Open Notifications - MS Teams settings and put web hook Url here
  • Test the hook url (you have to see the green result and the message in your Teams channel).

Login to ConnectWise as an Admin and select System -> Members -> API Members as shown below: 

Click on + as shown below: 

Fill out all required fields and click Save button: Be sure to set the permission to "Admin".

lick on API Keys and then click on the + sign to add a new key: 

Give it a description and click Save: 

The keys will disappear after you click save and close so copy both now to a document or directly into Alert Manager before you save and close in ConnectWise. 

Now login to Alert Manager and click on Integrations and click Add CRM

Select ConnectWise: 

Input the settings for your integration. Please note your URL and Company ID will be the same that you use to login to CW. Ours is a test system URL. 

Select your Ticketing Defaults

Once you have the ticketing profile setup you can utilize this profile for your notifications/tickets. You can also create additional ticketing profiles by going back into the integration. 

Click on Notifications and you can define the ticketing profile. You can setup multiple rules that target different views or uptime monitors. 

Ticketing can be created instantly or on a schedule and you can define the ticketing subjects etc. 

When creating ticket notifications, you can use the variables from emails you process to inject them directly into the subject or ticket description. 

In the example below you can click on the plus button next to Ticket Subject or Body and you can see the fields you have processed. In the case below you can select "What Happened", What SophosHasDoneSoFar and What you need to do and all of that data would go into the body of the ticket. You can leverage fields like "Company Name, What Happened and Urgency" in the ticket subject. For both fields you can utilize a mix of text and variables provided to get the most relevant information in the ticket. You could additionally link any processes that may be relevant to resolving the issue for your techs. 

The Email Date and URL are standard fields we provide that you can inject automatically in the ticket. 

Email Date provides the date/time stamp the email was received.

Email URL provides the user the ability to click and see the original email we processed as it came in with all information.  

Login to Autotask and create your API username and password: 

Under Admin -> Resources (Users) click on New and select "API User", Select Alert Manager as your integration partner, and generate a username and password. These two fields will be the username and password you will use to connect Alert Manager to Datto Autotask. 

Select Security Level "API User" (system)

In Alert Manager click on Integrations and click on Add CRM: 

Click on Autotask and then input the username and password from the steps above: 

Once you click submit you will be prompted to create a Ticketing profile. Below is a sample and you will just click the drop downs under each area you want to select defaults for on the ticketing. 

Once you click submit the integration is complete and can now be used for ticketing through our notifications section.

Under the Notifications menu you can create tickets for Email and Device Monitors that you'd like to create tickets automatically for in the system. 

Users can customize the ticketing subject and tickets can be set to be created instantly or on a schedule. 

For Email Alerts you can specify what statuses create a ticket in the system: 

For Device Monitor alerts MSPs can control how many failed alerts before a ticket is created or updated in the system. 

 
 
 
 

General Support

Create New Parser

Click on the subject of the email you wish to parse: 

 

Click on Add Parser

 

Once the parsing window opens up you will see tabs for HTML, Text, JSON and any document files showing. In this case we will select the Lead Document.docx file we wish to parse data from. 

Give the parser a name. For example if you were parsing Hubspot emails you might want to name it "Hubspot". In this case we have added two identifying rules to ensure that we process all emails that contain the subject and are from the right person. You can add one or more rules to ensure you only parse the emails that are needed. 

Click on Add Data Express and start selecting data from the email. 

 

Then select the data you wish to extract from the email or attachment. A pop up will show the name of the field if we are able to automatically determine it. If not you can customize the name yourself and click on the arrow to save it. 

 

You can adjust the settings to the right for how we process the data by selecting the occurrence. For example if there are more than one name in the email that you want to gather you can select all occurrences. If it is just this one you can select first occurrence or selected element. Click on Submit. Then click on test to verify that the data you are trying to parse is showing up properly. 

 You can see the output of the clicking test and we can see that it has properly parsed the name Patrick Leonard. 

 

We can now click on ADD DATA EXPR again to add more fields. 

Once you have selected all the fields you must also select at least one ID field in the field transformer. This is how the system will logically group the data you select for viewing. In general you could select a company name, persons name, date or anything else as an identifying field. You only need one but you can group by more than one ID field if needed. 

 

You should now see the email status as processed and the email parser you created assigned to that email. 

 

The system will now parse the fields selected and setup a data view for you to see the data you parsed. You can rename and change the fields that are displayed in the data view on screen or in the data views section.