What’s New

Here are our latest changes and improvements

Anodot API documentation now available as open source

  • APIs

😺 We’ve open sourced our API documentation

Following some good feedback we got from our customers (that’s you!) about our API documentation, we’ve decided to open-source it. It was originally based on Slate and we are now making it public. So – feel free to head out to the github repo and re-use at will. The full API is available, as always, at docs.anodot.com

What’s new for January 14

  • User Experience
  • Data Collection
  • Bug Fixes

💡New – Segment Collector

  • Anodot now supports collecting data directly from Segment. We are working together with Segment so that the collector is available as a Segment ‘destination’. Learn more here.

🗃 Feature Enhancements

  • Google Ads Collector new supports filtering of “active/paused” campaigns.
  • A new UX for stream scheduler (For now just for S3 streams).

🔔 New – System Notifications

  • We’ve introduced a special notification for stream owners when one of their streams is in error. Using these notifications, you dont need to define a ‘no data’ alert on streams just to make sure that they are OK. Learn more here.

🛠 Bug Fixes

  • Fixing the gradient color when hovering on a trigger in the alert console
  • Fixed timing of getting CUR files for the AWS Cloud Cost Monitoring
  • Fixed filter section handling small screen height
  • Fixed wrong font height in new data management page.
  • Fixed test size of link in the alert console

Better Metric Usage Reporting

  • Dashboards

In order to enable better reporting on how you use Anodot, We’ve added additional metrics to the service_usage metric. These metrics enables seeing how many metrics your account consumed according to the following dimensions – per stream, per alert and per composite. If you would like to find that stream which suddenly sending too much metrics – it is now very easy to see this data in the metric explorer, create a dashboard based on it or even better – define an alert based on it.

The feature is open to select customers. Please contact your Customer Success Manager if you would like to have it enabled in your account.

What’s new for the first week of January

  • User Experience
  • Data Collection
  • Bug Fixes

🗃 Feature Enhancements

  • Our Snowflake collector now supports Key-Pair Authentication. More details here.
  • We’ve added support for {{open_time}} and {{alert_time}} variables also in epoch format. More details here.

🔍 Alert Console Improvements

  • We’ve cleaned up the fields displayed per metric in the Alert console
  • Business Impact is now available in the Alert console

🛠 Bug Fixes

  • Not being able to choose to receive only OPEN notifications in No Data alert
  • New alert editor is changing alert configurations
  • Alert significance score can’t be edited without saving a new composite
  • Reduce “Composite: No data min duration (minutes)” – not taking under account the customer settings
  • Wrong influencing message when saving alert
  • When editing an S3 file, the schema mapping is not saved
  • summariseToDate enhancement + bug fix

The New Data Management Page is here

  • User Experience
  • Data Collection

🗃  New Data Management Page

We’ve revamped the Data Management page (formerly known as ‘Streams’) to enable better visibility of which data streams and sources you have sending metrics into Anodot.

BTW – For customers who are using Agents to send data to Anodot – Those are now visible in the Data Management page as well.

Learn More

Using Alert Variables

  • User Experience
  • Alerts Improvements

We’ve enriched the number of alert variables you can use when creating the titles and descriptions of alerts. Previously – you could add {{dimension_name}} to an alert description or name and Anodot would fill the relevant name of the dimension being triggered when sending you the notification. We’ve added a bunch of new variables: {{open_time}}, {{trigger_time}}, {{direction}} and more. These can come in very handy when creating a dynamic link to an external system for further investigation, e.g. you can put in the description a link which looks like:

https://grafana.mycompany.com/d/C9ypbqxMz/metrics-dashboards?country={{country}}&starttime={{open_time}}&endtime={{trigger_time}}

More details can be found here.