{"id":2413,"date":"2018-11-29T15:40:20","date_gmt":"2018-11-29T15:40:20","guid":{"rendered":"https:\/\/solutionsreview.com\/network-monitoring\/?p=2413"},"modified":"2018-11-29T15:50:07","modified_gmt":"2018-11-29T15:50:07","slug":"symptomatic-alerts-monitoring","status":"publish","type":"post","link":"https:\/\/solutionsreview.com\/network-monitoring\/symptomatic-alerts-monitoring\/","title":{"rendered":"Introduction to Symptomatic Alerts in Monitoring"},"content":{"rendered":"<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-2428\" src=\"https:\/\/solutionsreview.com\/network-monitoring\/files\/2018\/11\/An-Introduction-to-Symptomatic-Alerts-in-Monitoring.jpg\" alt=\"Symptomatic Alerts Monitoring\" width=\"800\" height=\"400\" srcset=\"https:\/\/solutionsreview.com\/network-monitoring\/files\/2018\/11\/An-Introduction-to-Symptomatic-Alerts-in-Monitoring.jpg 800w, https:\/\/solutionsreview.com\/network-monitoring\/files\/2018\/11\/An-Introduction-to-Symptomatic-Alerts-in-Monitoring-300x150.jpg 300w, https:\/\/solutionsreview.com\/network-monitoring\/files\/2018\/11\/An-Introduction-to-Symptomatic-Alerts-in-Monitoring-768x384.jpg 768w, https:\/\/solutionsreview.com\/network-monitoring\/files\/2018\/11\/An-Introduction-to-Symptomatic-Alerts-in-Monitoring-640x320.jpg 640w, https:\/\/solutionsreview.com\/network-monitoring\/files\/2018\/11\/An-Introduction-to-Symptomatic-Alerts-in-Monitoring-128x64.jpg 128w, https:\/\/solutionsreview.com\/network-monitoring\/files\/2018\/11\/An-Introduction-to-Symptomatic-Alerts-in-Monitoring-400x200.jpg 400w, https:\/\/solutionsreview.com\/network-monitoring\/files\/2018\/11\/An-Introduction-to-Symptomatic-Alerts-in-Monitoring-180x90.jpg 180w\" sizes=\"(max-width: 800px) 100vw, 800px\" \/><\/p>\n<p>Monitoring solutions give enterprise IT professionals a head start on outages and performance issues. One would expect <a href=\"https:\/\/solutionsreview.com\/network-monitoring\/machine-learning-network-monitoring\/\" target=\"_blank\" rel=\"noopener\">alerts<\/a> from a monitoring solution to be logical and important, but this isn&#8217;t always the case. To learn more about optimizing alerts for monitoring, we spoke with <a href=\"https:\/\/www.linkedin.com\/in\/james-sparenberg062017\/\" target=\"_blank\" rel=\"noopener\">James Sparenberg,<\/a> DevOps Engineer at Ericsson.<\/p>\n<p>James has years of experience as a Linux Admin. He has worked in Docker, Puppet, monitoring, troubleshooting, and much more.<\/p>\n<div class=\"hr hr\"><\/div>\n<p style=\"text-align: justify\">What are Symptomatic Alerts in Monitoring?\u00a0 It\u2019s monitoring and alerting designed to detect the symptoms of ill performance, not the exact cause of ill performance.\u00a0 By doing this it ensures that any alert you receive is actionable and catches any problems you have, not just the ones you are expecting.<\/p>\n<h5 style=\"text-align: justify\"><strong>Actionable Alerts<\/strong><\/h5>\n<p style=\"text-align: justify\">Alerting becomes the first step where we are analyzing the data we gathered in our monitoring.\u00a0 Here we want the following:<\/p>\n<ul style=\"text-align: justify\">\n<li>Alerts should be actionable \u2013 There should be an action or a series of actions that attach to all alerts. Informational alerts contribute to pager fatigue.<\/li>\n<li>Alerts should give you the 4 Ws \u2013 Who (the object name or other physical identifier), What (The event that triggered), When (The time it triggered), Where (location of documentation related to the monitor)<\/li>\n<li>Alerts should indicate that analysis must happen. If you do the analysis programmatically, then you should also write a program to automatically fix it. Cut the human out of the loop and put it in a report, not an alert<\/li>\n<\/ul>\n<p style=\"text-align: justify\">Actionable alerts are the first item.\u00a0 Let\u2019s take a database, you monitor the number of entries per minute.\u00a0 Your monitor reports the number of entries recorded in the last minute.\u00a0 This gives you 3 conditions of note. Low \u2013 High, and Average number of entries.\u00a0 Should you create an alert if the # of entries hits a high rate?\u00a0 Probably not.\u00a0 That is what you built a system for, to handle spikes, at 3am do you care if suddenly people are ordering the new iWidget for their Holiday shopping?\u00a0 Yes, if you oversee logistics for delivery.\u00a0 But at 3am, you aren\u2019t going to stop people from shopping (or at 3pm for that matter) so why alert and wake someone up?\u00a0 Simply log it, chart it, and use it for capacity planning and growth later.<\/p>\n<h5 style=\"text-align: justify\"><strong>Low (or no) entry alerts<\/strong><\/h5>\n<p style=\"text-align: justify\">Now comes the second alert possibility.\u00a0 Low (or no) entries.\u00a0 This could be just coincidence, as no one is up at 3am this morning.\u00a0 It could be your threshold is too high (Action = adjust threshold).\u00a0 It could be the frontend not sending data too your DB, because the overseas team put a typo into the code they just pushed (it\u2019s their afternoon).\u00a0 The low number of entries requires you to take action and analyze why the number has gone south.\u00a0 This is an actionable alert, and the kind we want to be woken up for. (NOTE: This is likely an error that should have been caught by CI-CD but that\u2019s another topic)<\/p>\n<p style=\"text-align: justify\">Alerts requiring action, (tests, log checks, etc) don\u2019t cause people to just acknowledge and go back to sleep without fully comprehending the alert.\u00a0 They instead cause them to find solutions that will prevent the next alert of this kind, or otherwise contribute to an increase in performance of the system.<\/p>\n<div class=\"widget\"><div class=\"aside-card\">\t\t\t<div class=\"textwidget\"><p><a class=\"nm-speedbump\" title=\"Download link to Network Monitoring Buyer's Guide\" href=\"https:\/\/solutionsreview.com\/network-monitoring\/get-a-free-network-monitoring-buyers-guide\/\" target=\"_blank\" rel=\"noopener\"><img loading=\"lazy\" decoding=\"async\" class=\"alignleft size-full wp-image-1682\" src=\"https:\/\/solutionsreview.com\/network-monitoring\/files\/2021\/04\/Network_Monitoring_Buyers_Guide_Bump_800.gif\" alt=\"Download Link to Data Integration Buyers Guide\" width=\"800\" height=\"100\" \/><\/a><\/p>\n<\/div>\n\t\t<\/div><\/div>\n<h5 style=\"text-align: justify\"><strong>Monitor everything, alert selectively<\/strong><\/h5>\n<p style=\"text-align: justify\">This follows the credo of monitor everything, alert only on those things that need action to be taken.\u00a0 We can create a graph of data entry rate over time, see that we are getting peaks at 90% of capacity for 4 hours a data, and find a way to automate that capacity increase to ensure we never go above 70% for longer than 10 minutes, and we should.\u00a0 But we don\u2019t want to make the method of increasing capacity, having our admin build a new DB server and put it online at 3am.<\/p>\n<p style=\"text-align: justify\">Conversely, at 3am 0 data input is something that immediately affects the companies bottom line.\u00a0 This requires action to be taken now to resolve the problem.\u00a0 Customers are affected.\u00a0 Customers drive your reason to work.\u00a0 Action is required.<\/p>\n<p style=\"text-align: justify\">Let\u2019s take a look at the two ways in which we could setup our alert.<\/p>\n<ul style=\"text-align: justify\">\n<li>Event based \u2013 we monitor to see if the URL the frontend has, is correct for the DB. Then act<\/li>\n<li>Symptom based \u2013 we monitor for the symptom that indicates a problem (Low or no data entries in X timeframe) and action is taken<\/li>\n<\/ul>\n<p style=\"text-align: justify\">Both cases are actionable events, so that requirement is met.\u00a0 The problem comes from the first item. It violates the rule of no analysis.\u00a0 Additionally, it would require you add rules for each the other causes of frontend to backend loss of entries being made (with more time taken to write and test each and every possibility).\u00a0\u00a0 More rules cause more load on your alert system (each rule having to be run against the data set for each event until you either run out of rules or a match is made).\u00a0 This loads up your monitoring system and adds delay to your ability to get the problem solved increasing income loss.<\/p>\n<h5 style=\"text-align: justify\"><strong>Symptomatic monitoring<\/strong><\/h5>\n<p style=\"text-align: justify\">In symptom-based monitoring you would instead be monitoring for 3 events. \u00a0For example, 500 errors on the app servers, low data entry on the DB and backend errors in logs.\u00a0 Then alerting on 2 of them (500 errors and low data rate), possibly backend errors as well (dependent on the setup).\u00a0 This is 3 total rules, which would cover every possible cause, instead of 1 rule for each possible cause.<\/p>\n<p style=\"text-align: justify\">The only thing worse than having an alarm go off at 3am, is not having one go off when it should have.\u00a0 If you are monitoring for a specified problem, you will catch that problem.\u00a0 However, you also will miss when the condition that is a problem exists, from a different cause.<\/p>\n<p style=\"text-align: justify\">At this point, one hopes that you have a well-formed alert.\u00a0 It tells people when and where the problem is, and correctly points them at any docs related to the alert.\u00a0 The docs would then become the source of exact causes(s) of the problem and instructions on how to handle the problem.<\/p>\n<p style=\"text-align: justify\">The TL:DR of all this is.\u00a0 Monitor for conditions and symptoms of a non-performant environment, over trying to write individual rules for every possible cause of a non-performant system.\u00a0 The end result will be a smaller rule set that covers all causes. Does so in less time, resulting in a smaller footprint on your network of applications.<\/p>\n<div class=\"widget\"><div class=\"aside-card\">\t\t\t<div class=\"textwidget\"><p><a class=\"nm-speedbump\" title=\"Download link to Network Monitoring Buyer's Guide\" href=\"https:\/\/solutionsreview.com\/network-monitoring\/get-a-free-network-monitoring-buyers-guide\/\" target=\"_blank\" rel=\"noopener\"><img loading=\"lazy\" decoding=\"async\" class=\"alignleft size-full wp-image-1682\" src=\"https:\/\/solutionsreview.com\/network-monitoring\/files\/2021\/04\/Network_Monitoring_Buyers_Guide_Bump_800.gif\" alt=\"Download Link to Data Integration Buyers Guide\" width=\"800\" height=\"100\" \/><\/a><\/p>\n<\/div>\n\t\t<\/div><\/div>\n","protected":false},"excerpt":{"rendered":"<p>Monitoring solutions give enterprise IT professionals a head start on outages and performance issues. One would expect alerts from a monitoring solution to be logical and important, but this isn&#8217;t always the case. To learn more about optimizing alerts for monitoring, we spoke with James Sparenberg, DevOps Engineer at Ericsson. James has years of experience [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":2428,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"inline_featured_image":false,"footnotes":""},"categories":[1],"tags":[33,379,455],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v23.5 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>An Introduction to Symptomatic Alerts in Monitoring<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/solutionsreview.com\/network-monitoring\/symptomatic-alerts-monitoring\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"An Introduction to Symptomatic Alerts in Monitoring\" \/>\n<meta property=\"og:description\" content=\"Monitoring solutions give enterprise IT professionals a head start on outages and performance issues. One would expect alerts from a monitoring solution to be logical and important, but this isn&#8217;t always the case. To learn more about optimizing alerts for monitoring, we spoke with James Sparenberg, DevOps Engineer at Ericsson. James has years of experience [&hellip;]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/solutionsreview.com\/network-monitoring\/symptomatic-alerts-monitoring\/\" \/>\n<meta property=\"og:site_name\" content=\"Network Monitoring Tools &amp; Performance Software | Solutions Review\" \/>\n<meta property=\"article:published_time\" content=\"2018-11-29T15:40:20+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2018-11-29T15:50:07+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/solutionsreview.com\/network-monitoring\/files\/2018\/11\/An-Introduction-to-Symptomatic-Alerts-in-Monitoring.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"800\" \/>\n\t<meta property=\"og:image:height\" content=\"400\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Doug Atkinson\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Doug Atkinson\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"5 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/solutionsreview.com\/network-monitoring\/symptomatic-alerts-monitoring\/\",\"url\":\"https:\/\/solutionsreview.com\/network-monitoring\/symptomatic-alerts-monitoring\/\",\"name\":\"An Introduction to Symptomatic Alerts in Monitoring\",\"isPartOf\":{\"@id\":\"https:\/\/solutionsreview.com\/network-monitoring\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/solutionsreview.com\/network-monitoring\/symptomatic-alerts-monitoring\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/solutionsreview.com\/network-monitoring\/symptomatic-alerts-monitoring\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/solutionsreview.com\/network-monitoring\/files\/2018\/11\/An-Introduction-to-Symptomatic-Alerts-in-Monitoring.jpg\",\"datePublished\":\"2018-11-29T15:40:20+00:00\",\"dateModified\":\"2018-11-29T15:50:07+00:00\",\"author\":{\"@id\":\"https:\/\/solutionsreview.com\/network-monitoring\/#\/schema\/person\/5992f02d38e7b28251ad933cd131dcae\"},\"breadcrumb\":{\"@id\":\"https:\/\/solutionsreview.com\/network-monitoring\/symptomatic-alerts-monitoring\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/solutionsreview.com\/network-monitoring\/symptomatic-alerts-monitoring\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/solutionsreview.com\/network-monitoring\/symptomatic-alerts-monitoring\/#primaryimage\",\"url\":\"https:\/\/solutionsreview.com\/network-monitoring\/files\/2018\/11\/An-Introduction-to-Symptomatic-Alerts-in-Monitoring.jpg\",\"contentUrl\":\"https:\/\/solutionsreview.com\/network-monitoring\/files\/2018\/11\/An-Introduction-to-Symptomatic-Alerts-in-Monitoring.jpg\",\"width\":800,\"height\":400,\"caption\":\"Symptomatic Alerts Monitoring\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/solutionsreview.com\/network-monitoring\/symptomatic-alerts-monitoring\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/solutionsreview.com\/network-monitoring\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Introduction to Symptomatic Alerts in Monitoring\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/solutionsreview.com\/network-monitoring\/#website\",\"url\":\"https:\/\/solutionsreview.com\/network-monitoring\/\",\"name\":\"Network Monitoring Tools &amp; Performance Software | Solutions Review\",\"description\":\"Evaluating Enterprise NPM Software, Network Observability &amp; Packet Analysis Tools.\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/solutionsreview.com\/network-monitoring\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/solutionsreview.com\/network-monitoring\/#\/schema\/person\/5992f02d38e7b28251ad933cd131dcae\",\"name\":\"Doug Atkinson\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/solutionsreview.com\/network-monitoring\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/092cfcbe5c7f2c185c21f152aada2d2f?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/092cfcbe5c7f2c185c21f152aada2d2f?s=96&d=mm&r=g\",\"caption\":\"Doug Atkinson\"},\"description\":\"An entrepreneur and executive with a passion for enterprise technology, Doug founded Solutions Review in 2012. He has previously served as a newspaper boy, a McDonald's grill cook, a bartender, a political consultant, a web developer, the VP of Sales for e-Dialog - a digital marketing agency - and as Special Assistant to Governor William Weld of Massachusetts.\",\"sameAs\":[\"https:\/\/solutionsreview.com\"],\"url\":\"https:\/\/solutionsreview.com\/network-monitoring\/author\/doug-atkinson-4\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"An Introduction to Symptomatic Alerts in Monitoring","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/solutionsreview.com\/network-monitoring\/symptomatic-alerts-monitoring\/","og_locale":"en_US","og_type":"article","og_title":"An Introduction to Symptomatic Alerts in Monitoring","og_description":"Monitoring solutions give enterprise IT professionals a head start on outages and performance issues. One would expect alerts from a monitoring solution to be logical and important, but this isn&#8217;t always the case. To learn more about optimizing alerts for monitoring, we spoke with James Sparenberg, DevOps Engineer at Ericsson. James has years of experience [&hellip;]","og_url":"https:\/\/solutionsreview.com\/network-monitoring\/symptomatic-alerts-monitoring\/","og_site_name":"Network Monitoring Tools &amp; Performance Software | Solutions Review","article_published_time":"2018-11-29T15:40:20+00:00","article_modified_time":"2018-11-29T15:50:07+00:00","og_image":[{"width":800,"height":400,"url":"https:\/\/solutionsreview.com\/network-monitoring\/files\/2018\/11\/An-Introduction-to-Symptomatic-Alerts-in-Monitoring.jpg","type":"image\/jpeg"}],"author":"Doug Atkinson","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Doug Atkinson","Est. reading time":"5 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/solutionsreview.com\/network-monitoring\/symptomatic-alerts-monitoring\/","url":"https:\/\/solutionsreview.com\/network-monitoring\/symptomatic-alerts-monitoring\/","name":"An Introduction to Symptomatic Alerts in Monitoring","isPartOf":{"@id":"https:\/\/solutionsreview.com\/network-monitoring\/#website"},"primaryImageOfPage":{"@id":"https:\/\/solutionsreview.com\/network-monitoring\/symptomatic-alerts-monitoring\/#primaryimage"},"image":{"@id":"https:\/\/solutionsreview.com\/network-monitoring\/symptomatic-alerts-monitoring\/#primaryimage"},"thumbnailUrl":"https:\/\/solutionsreview.com\/network-monitoring\/files\/2018\/11\/An-Introduction-to-Symptomatic-Alerts-in-Monitoring.jpg","datePublished":"2018-11-29T15:40:20+00:00","dateModified":"2018-11-29T15:50:07+00:00","author":{"@id":"https:\/\/solutionsreview.com\/network-monitoring\/#\/schema\/person\/5992f02d38e7b28251ad933cd131dcae"},"breadcrumb":{"@id":"https:\/\/solutionsreview.com\/network-monitoring\/symptomatic-alerts-monitoring\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/solutionsreview.com\/network-monitoring\/symptomatic-alerts-monitoring\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/solutionsreview.com\/network-monitoring\/symptomatic-alerts-monitoring\/#primaryimage","url":"https:\/\/solutionsreview.com\/network-monitoring\/files\/2018\/11\/An-Introduction-to-Symptomatic-Alerts-in-Monitoring.jpg","contentUrl":"https:\/\/solutionsreview.com\/network-monitoring\/files\/2018\/11\/An-Introduction-to-Symptomatic-Alerts-in-Monitoring.jpg","width":800,"height":400,"caption":"Symptomatic Alerts Monitoring"},{"@type":"BreadcrumbList","@id":"https:\/\/solutionsreview.com\/network-monitoring\/symptomatic-alerts-monitoring\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/solutionsreview.com\/network-monitoring\/"},{"@type":"ListItem","position":2,"name":"Introduction to Symptomatic Alerts in Monitoring"}]},{"@type":"WebSite","@id":"https:\/\/solutionsreview.com\/network-monitoring\/#website","url":"https:\/\/solutionsreview.com\/network-monitoring\/","name":"Network Monitoring Tools &amp; Performance Software | Solutions Review","description":"Evaluating Enterprise NPM Software, Network Observability &amp; Packet Analysis Tools.","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/solutionsreview.com\/network-monitoring\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/solutionsreview.com\/network-monitoring\/#\/schema\/person\/5992f02d38e7b28251ad933cd131dcae","name":"Doug Atkinson","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/solutionsreview.com\/network-monitoring\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/092cfcbe5c7f2c185c21f152aada2d2f?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/092cfcbe5c7f2c185c21f152aada2d2f?s=96&d=mm&r=g","caption":"Doug Atkinson"},"description":"An entrepreneur and executive with a passion for enterprise technology, Doug founded Solutions Review in 2012. He has previously served as a newspaper boy, a McDonald's grill cook, a bartender, a political consultant, a web developer, the VP of Sales for e-Dialog - a digital marketing agency - and as Special Assistant to Governor William Weld of Massachusetts.","sameAs":["https:\/\/solutionsreview.com"],"url":"https:\/\/solutionsreview.com\/network-monitoring\/author\/doug-atkinson-4\/"}]}},"_links":{"self":[{"href":"https:\/\/solutionsreview.com\/network-monitoring\/wp-json\/wp\/v2\/posts\/2413"}],"collection":[{"href":"https:\/\/solutionsreview.com\/network-monitoring\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/solutionsreview.com\/network-monitoring\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/solutionsreview.com\/network-monitoring\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/solutionsreview.com\/network-monitoring\/wp-json\/wp\/v2\/comments?post=2413"}],"version-history":[{"count":0,"href":"https:\/\/solutionsreview.com\/network-monitoring\/wp-json\/wp\/v2\/posts\/2413\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/solutionsreview.com\/network-monitoring\/wp-json\/wp\/v2\/media\/2428"}],"wp:attachment":[{"href":"https:\/\/solutionsreview.com\/network-monitoring\/wp-json\/wp\/v2\/media?parent=2413"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/solutionsreview.com\/network-monitoring\/wp-json\/wp\/v2\/categories?post=2413"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/solutionsreview.com\/network-monitoring\/wp-json\/wp\/v2\/tags?post=2413"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}