What’s New

Here are our latest changes and improvements

What’s New for August 10th – Revenue

  • User Experience
  • Data Collection
  • APIs
  • Bug Fixes
  • Revenue

:gift: New Features

  • We have a new agent enabling you to get data from Apache Impala.
  • We are happy to introduce our new ServiceNow channel!
  • We’ve added a new API which enables you to create a user in Anodot via the API. Very useful if you want to automate the provisioning of users.
  • We’ve also added an API enabling you to create groups.

:card_file_box: Improvements

  • We have improved the ‘influencing events’ feature so that you can now define multiple influencing events conditions on the same alert.
  • We made additional (minor) improvements to the UX of the Segment collector. The Segment collector now supports three collection intervals – 1 minutes, 5 minutes and hourly.
  • We improved the channel search so that it is case insensitive (Like the stream search)
  • We’ve improved tag support to agents.
  • We’ve improved the wording on the stream status notification emails

:hammer_and_wrench: Bug Fixes

  • We fixed an issue which caused deleted metrics to linger on. Parting is such a sweet sorrow.
  • We fixed an issue which prevented the business impact from being calculated correctly in some cases.
  • We fixed a bug which caused the text in one of the buttons in the File upload screen to disappear.
  • We fixed an issue when trying to add multiple alert variables to an expression.
  • We fixed an issue with alert variables drop down to only use the dimensions used in the expressions.
  • We fixed a nasty nasty bug with events which prevented them from showing up in the alert editor.
  • We fixed a bug in the channels management page where the ‘slack app’ did not appear in the channel type filter.
  • Fixed an issue which caused triggers to be sent to multiple slack channels (when using the ‘ungroup by metric’ feature)
  • We filled some UX issues when using the ‘fill the gaps’ feature
  • We fixed an issue which could have caused issues when using SSO in multi-account scenarios.
:earth_africa: As usual – All the release features, beta features, upcoming features and all your feature requests can be found in our Product Portal.

What’s New for August 9th – Cost

  • User Experience
  • Bug Fixes
  • Cost
  • Recommendations

:gift: New Features

  • New Look for our UI: We’ve enhanced our application design. You’ll find everything in the same place as before, but our design team has taken steps to brighten the interface and make it more inviting. We hope you enjoy the new look.
  • New API documentation: is now available at https://docs.anodot.com/#cost

:card_file_box: ENHANCEMENTS

  • Reports: Account ID and name are now separated to 2 different columns.
  • Performance: enhanced queries caching and other improvements introduced to get quicker response time and efficient invoice processing.
  • Commitments: RI utilization for Azure is now available.
  • MSP: Scroll bar & Search box were added for browsing easier between accounts.

:hammer_and_wrench: BUG FIXES

  • Cost & Usage: Report download, fixed an issue where months order was wrong.
  • Recommendations: Fixed an issue where annual expected saving percentage from total, was wrongly calculated.
  • Recommendations: Enhanced explanation for Old KMS and CloudTrail duplicated trails recommendations.

What’s New for July 13th – Revenue

  • User Experience
  • Data Collection
  • Bug Fixes
  • Revenue

🎁 New Features

  • A new alert agent added to Anodot, consuming data from PRTG network management.
  • Showing missing data settings (DVP) in stream summary and pipeline summary

🗃 Improvements

  • We added auto-casting of BigDecimal values to float to overcome the JDBC driver failures on BigDecimals.
  • We have improved the SNMP agent configuration file structure.
  • We added the capability to set the agent log level using environment variables
  • The agent configuration now allows 1-minute filling of data gaps.
  • We have improved the way pipeline configuration information is shown in the pipeline summary modal. We also enabled editing the impact from the modal.

🛠 Bug Fixes

  • We have improved the dashboard time-frame control stability
  • Fixed a bug to allow comma values within regex in the Kafka agent transformation module
  • We fixed a bug in raw-pipelines.
  • Fixed an issue in the filtering of the anomaly tile.
  • We fixed an issue where public dashboards did require a login (Yes, there is a such a thing ‘too secure’)
  • We have improved the handling of telegram group id changes
  • We fixed the image URL in our test message in channels.
  • Standard users could accidentally edit the stream or pipeline owner and access group. We fixed it so only admins can do it.
  • We had an issue showing trigger content in some scenarios, it was fixed.
  • Using the new event conditions, a single condition could not be removed from the alert, it can be removed now.
  • We fixed a bug where long expressions were hard to enter, the search expression is much easier to use now. Notice the scroll bar on the right if the expression is long.

What’s New for July 13th – Cost

  • Bug Fixes
  • Dashboards
  • Cost
  • MSP

:card_file_box:Enhancements

  • Cost & Usage: Allow viewing a panel without adding it to dashboard.
  • Adjust terminology of ‘linked account’ to be ‘subscriptions’ in Azure reports.

:hammer_and_wrench:Bug Fixes

  • Recommendations: Report was not sent automatically. This is now fixed.
  • Recommendations: EBS Upgrade, fixed format issue.
  • Recommendations: Azure, Cosmo DB Rightsizing improvements.
  • Users: Allow users with Viewer role to set their own notifications.
  • MSP: Credits grant could only be attributed to current month onwards.
  • MSP: Re-billing, fixed an issue with billing processing.
  • Budget Alert for Azure failed to be sent. This was fixed.
  • Budget: Fixed an issue with budget editing.
  • Cost & Usage Explorer: Fixed an issue for events display.
  • Cost Center API – Fixed a problem with the PUT API for updating LinkedAccount IDs.
  • Dashboard page in Cost & Usage menu was reviewed and aligned for better usability.
  • Fixed several problems for reports and alerts sending.

What’s New for July 6th

  • User Experience
  • Data Collection
  • APIs
  • Bug Fixes
:gift: New Features
  • We have added a new service usage metric – Anomalies. This will enable you to monitor how many anomalies Anodot found in your account for a specific date (and compare to how many triggers you got).
  • Triage is ready from prime time! This means that in the next few days, we will be replacing the ‘investigate’ buttons in all channels with the new ‘triage’ buttons. This includes emails, slack, webhook and all the channels.
  • Following the release of triage for ‘no data’ and ‘static’ triggers – you can also give feedback to these triggers. These feedback are not going to be used by our machine learning algorithms, but will help customers keep track of issues in their business using Anodot.
:card_file_box: Improvements
  • We’ve added a new filter – ‘contains’ to replace and filter by lookup table in Anodot streams.
  • We hardened our password policy to meet our security standards. There are two main changes:
    • Minimum of ten (10) characters in length for regular users
    • Minimum of fourteen (14) or more characters for service accounts, system-to-system accounts and administrative users.
  • We’ve improved our API documentation (docs.anodot.com) so that it is better organized and also includes the Cost API documentation. This is still WIP, so bear with us until it is fully done.
  • We have a new Grafana version (Release 4.0.2 of data plugin and 2.0.1 of panel plugin) with the following improvements:
    • Ability to control tooltip format (in metrics pane)
    • Ability to choose more than one dimension (in metrics pane)
    • Ability to filter anomalies by dimension (anomalies pane)
    • Apply variable switcher also for the anomalies pane
  • We added support to hourly collection for the Google GA4 collector
  • We Improved the alert status indication in Microsoft teams messages using color coding
  • We did some UX improvements in the incident tab of Triage.
  • Send message per metric is now supported in the Mattermost and Slack channels.
:hammer_and_wrench: Bug Fixes
  • We found an issue where non admin users were able to create Big Query streams. That’s a big no-no so we fixed it.
  • We improved handling comma within dimension/measure values before injecting metrics to Anodot
  • Eliminated general error when getting to the timeline tab in the triage as well as some pesky tooltip issues.
  • Fixed an issue with the google search collector where it was asking the wrong scope.
  • Filter by a non-existing label, now fetches all the triggers.
  • Fixing alert timeline sort order as well as the ‘alert close’ events not appearing in the right place.
  • Fixed an issue with Google Search Console collector when using an Invalid source account.
  • Fixes to recipient drop-down list presentation in the alert editor as well as the feedback pop-up.
  • We fixed an issue in the GA4 data source where changes in measures & dimensions create a faulty stream.
  • Tag value was shown with a redundant #, we fixed that.
  • Fixed a bug that prevented the pipeline owner from receiving notifications about the pipeline status
  • Fixed an issue with the time frame in the dashboards
  • Fixed several issues which occurred when importing dashboards.
  • Fixed an issue with the error reporting of the New Relic collector.
  • Fixed an issue which caused Composite validation errors not to be shown to the user.
  • Impact tended to disappear from the triage. Not anymore!
  • The Alert summary in Alert management showed “Delta Duration” even if the condition was not turned on. Fixed that.

What’s new for June 22nd

  • User Experience
  • Data Collection
  • Bug Fixes

🎁 New Features

  • We now support multiple accounts via Okta apps.
  • A new collector – Google Search Console!
  • Admins will now get a system notification when an alert or a composite go into error state. Everything to make your life easier.
  • [BETA] Triage for No data and static is here! We are slowly opening this to analyze the impact on performance.

🗃 Improvements

  • We improved the way channel names are displayed in the Anodot legacy Slack integration.
  • Major improvements to the Google GA4 collector.
  • Microsoft Teams alerts now color the message according to the alert status.
  • Segment collector can now use a sample file as input and the user can configure collection delay.
  • We’ve added to the System notifications a notification when a stream resumes collection.
  • Agents now support all UTF-8 characters. Go wild with those Hebrew based metrics!
  • We improved the integrations in the SNMP agent.
  • You can now set the log level of an agent as an environment variable.

🛠 Bug Fixes

  • We fixed an issue where in some cases the metrics selector was not clickable in some of the dashboards.
  • We fixed an issue in the Telegram messenger channel which caused the alert console to open with the wrong filter.
  • We fixed an issue with the agent where the start endpoint returns HTTP 500 is the pipeline is already running.
  • We fixed an issue which prevented users from duplicating Google Auctions streams.
  • We fixed an issue where the impact of an alert was missing from the triage.
  • We fixed an issue with the New Relic collector error handling.
  • We fixed an issue around using the username/pass when pinging for connection validation in the influxDB agent

What’s New for June 8th

  • User Experience
  • Data Collection

🎁 New Features

We have two new channels!
  • Telegram messenger is now supported. Documentation can be found here.
  • Mattermost is now supported. Documentation can be found here.

🗃 Improvements

  • Snowflake collector supports a new region – South Central US (Texas)
  • We’ve made various improvements to the the pie chart tile, including the ability to show forecast results.
  • Our agents now support python 3.10

🛠 Bug Fixes

  • Several improvements to the Assignee and recipient filter in the Alert console.
  • We fixed a nagging issue in the dashboard hover drop menu.
  • We fixed an issue with the topology map where nodes and cells weren’t shown.
  • We fixed an issue which caused the influencing metric condition on static alerts not to work properly.
  • Agents cli now allow a trailing slash in the destination URL.
  • Some additional issues related to agent monitoring have been fixed as well.
🌍 As usual – All the release features, beta features, upcoming features and all your feature requests can be found in our Product Portal. 

What’s New for May 25th

  • User Experience
  • Data Collection
  • Bug Fixes

🎁 New Features

  • We’ve added support to the SalesForce collector to work against sandbox accounts and while we were at it, we fixed a bug which prevented creating new SalesForce streams in the Frankfurt and Oregon environments.
  • You are now able to delete data sources of agent pipelines from the UI.

🗃 Improvements

  • The File Directory agent now supports sparse data handling (a.k.a. DVP)
  • Events now show up properly in the timeline.
  • We’ve adapted the Google Auctions insights collector to the new format introduced by Google recently.
  • We’ve improved the JDBC agent to support proxy config also for the watermark stage as well as improving the performance of the MS-SQL queries.
  • We’ve improved the ability to query managed accounts in Google Ads.

🛠 Bug Fixes

  • Moving between alerts in an alert group in the triage was faulty. Not anymore!
  • Several bugs in the new GA4 collector were found and fixed.
  • We fixed an issue in the topology map where alerted sites were not colored properly.
  • We fixed an issue with the Sage agent of handling creation when the query file is missing.
🌍 As usual – All the release features, beta features, upcoming features and all your feature requests can be found in our Product Portal. 

What’s New for May 11th

  • User Experience
  • APIs
  • Bug Fixes

🎁 New Features

  • Our PowerBI connector just got published on GitHub. With it you can get Anodot data into your PowerBI dashboards. Documentation can be found here.
  • You can now ungroup alerts by metric. This means that if we detect an incident on three different metrics – instead of one alert you will get three of them. Applicable for Slack, Jira, Microsoft Teams and Webhook channels.
  • New collector – we’ve added support to Google GA4.
  • A new public API for Topology. Huzzah!

🗃 Improvements

  • Our dashboards support public sharing, but in case you want to disable public sharing – this can now be configured in the account settings.
  • We’ve improved the alert assignment filters in the alert console.
  • Alert update as a notification option is now set ‘on’ as default.
  • We’ve added an option to the JDBC agent to calculate watermark based on the timezone.
  • Agents now make sure to update status whenever the agent container starts.
  • Agents are now monitoring metrics lag, so we are better able to track if they have such an issue.

🛠 Bug Fixes

  • We fixed an issue when removing an assignee in the alert console caused a ‘general error’.
  • We fixed some issues around influencing events – the simulation was not refreshing and some events were disappearing. Not anymore!
  • Several issues with Feedbacks in the alert console were addressed.
  • We fixed an issue where trigger timestamps in the alert management screen were not aligned with the user time zone.
  • We fixed an issue with the influx agent which caused an exception when updating the pipelines.
  • We fixed issues related to the connection between alert and dashboard.
  • Did we finally get the ‘refresh’ button in Metric Explorer to work? Only time will tell. But we are optimistic.

🌍 As usual – All the release features, beta features, upcoming features and all your feature requests can be found in our Product Portal. 

What’s New for April 27th

  • User Experience
  • APIs
  • Bug Fixes
  • Dashboards

🎁 New Features

  • You can now export a timeline to a CSV file. Super useful for retrospectives.What’s New for April 27th
  • You can now see business events in the alert console. This is part of our enhanced support for new types of business events.
  • A new API showing the anomalies count in an account.

🗃 Improvements

  • You may have noticed that when giving feedback from an email – there is a brand new page to capture why you thought this alert was important for your business (or not!).
  • We’ve added Metrics 3.0 support to the MS-SQL agent.
  • Observium agent not replaces empty tags with NULL and filters empty string dimensions.
  • VictoriaMetrics agent now supports handling sparse data streams.
  • We’ve improved the behaviour of the ‘summarizeToDate’ function.
  • We’ve improved the error message in the agent CLI.
  • We’ve disabled the ‘duplicate’ function for several channels. This is done for channels where you need dedicated authentication information, in order not to use the same authentication for multiple channels.

🛠 Bug Fixes

  • We fixed an issue in the create event API
  • We fixed an issue in the metrics explorer which prevent some dimensions from being selected. There was also an issue with the 2nd expression in the metrics explorer misbehaving. Fixed as well.
  • Some minor UX improvements in the Share dashboard dialog.
  • Some UX improvements the the Pie charts tile.
  • We fixed an issue where the there was no progress bar when uploading a CSV.
  • We fixed an issue with the ‘Primary’ action in emails. There was also an issue with the ‘Dashboard’ link from emails which wasn’t working properly – this is not fixed as well.
  • We fixed an issue with the Divert Stream API where it didn’t work correctly with incomplete streams.
  • Fixed an issue with dashboards filters not showing all the possible dimension values.
  • Fixed an issue with the Coralogix collector not showing dimensions for new metrics.
  • We fixed various errors related to the Insight panel which caused a ‘general error’ to show up in some cases.
  • We fixed an issue with searching by labels in the alert console.
  • Last but not least – we fixed an issue where deleting a schema which no longer sends data to Anodot causes an error. No more Zombie schemas! 🧟‍♂️


🌍 As usual – All the release features, beta features, upcoming features and all your feature requests can be found in our
Product Portal. 

What’s New for March 30th

  • User Experience
  • Data Collection
  • APIs
  • Bug Fixes
  • Dashboards

🎁 New Features

  • A new API – divert streams API – Moving a stream from one source to another. Documentation can be found here.
  • PromQL Agent now enables adding HOST headers for connection to prometheus.
  • A new agent for RRD files.
  • Observium agents now allow measurement transformations as well as skipping non-type values in measurements.
  • A new service_usage metric has been added – ‘triggered‘ which enables you to see how many alerts were triggered based on type (Anomaly, static, noData)

What’s New for March 30th

🗃 Improvements

  • We’ve improved the behavior of the ‘minimize’ functionality in triage.
  • We’ve improved the filters in the alert console for Alert Assignment as well as the severity view.
  • We’ve made some UX improvements to the alert console, especially around the alignment of the ‘Ack’, ‘Snooze’ buttons.
  • We’ve improved the behavior when someone chooses ‘acknowledge’ from an alert assignment email.
  • We improved the ‘select / clear all’ behavior when editing a graph tile and when seeing a graph tile in a dashboard.

🛠 Bug Fixes

  • We fixed an issue in the Kafka agent where the send_watermark script didn’t use the proxy.
  • We fixed an issue related to alert console sorting.
  • Several fixes to the alert editor.
  • Several fixes to the activity log.
  • We’ve fixed an issue which prevented sending ‘Good’ feedback from iPhone.
  • We fixed an issue which prevented duplicating Sumo Logic streams.

🌍 As usual – All the release features, beta features, upcoming features and all your feature requests can be found in our Product Portal. 

What’s New for March 10th

  • User Experience
  • APIs
  • Bug Fixes
  • Dashboards

It’s DST time again! 🌞

  • In the next couple of weeks, daylight savings time will go into effect in the US and later also in Europe. Naturally, a change in time zones may have an impact on any metric which has hourly seasonality. However – No need to worry. Our customer success & support team will be making sure to adjust the baselines to handle this change.

🗃 Improvements

  • Based on popular demand, you can now create dashboard filters based on tags and not just metric dimensions. We’ve also fixed the ‘select all’ and ‘clear all’ in the filters.
  • More in dashboards – You can now export a tile to CSV. Huzzah!
  • Last one in dashboards (at least for this week) – We’ve redesigned the user experience of setting a time frame for a tile. We hope the new design makes more sense.
  • Our Google Auction Insights collector now supports collecting historical data.
  • Searching for an expression in the alert editor just got better – we improved coverage to several use cases.
  • We’ve improved the way metrics sent from APIs are presented in Anodot. When you send metrics using the Anodot REST API, each schema you use will be shown as a separate ‘stream’ in Anodot.
  • We improved the way units are presented in dashboards. In general – Setting a unit to your metrics will improve the readability of alerts and dashboards to your end user.
  • A new API – Alert Assignment API. For those of you who already using the Alert Assignment feature, you can now change the assignment from one user to another using an API (soon – also from Slack).
  • Last but not least – We’ve improved the way time zones are displayed for users in the settings page (to support 24hr format). The time zone settings are now also displayed as part of the user information. This feature the traditional “Nadav’s birthday feature”. Happy birthday Nadav! 🎉

🛠 Bug Fixes

  • We fixed an issue in the way alerts were sorted in the Severity View.
  • We improved the format of the Alert Assignment email.
  • We improved the error messages user get when they try to to create alerts and have no permissions.
  • We fixed an issue which caused users to get ‘general error’ when editing certain dashboards.
  • We fixed an error which which some users experienced when using the ‘snooze’ functionality.
  • We fixed several issues in the recipients drop down when editing and creating alerts.
  • There was an issue in the data streams page where it showed wrong headers on the table.
  • We fixed an issue where setting the the Y axis range in metric explorer was not working well.
  • We fixed an issue where searching an alert which contained the ‘[‘ symbol caused an error. How embarrassing 🤦‍♂️

🌍 As usual – All the release features, beta features, upcoming features and all your feature requests can be found in our Product Portal. 

What’s New for January 30th

  • User Experience
  • Data Collection
  • Bug Fixes

🎁 [BETA] Alert Assignment is here!

A big part of part of handling incidents is understanding ownership. Who is the person who takes care of a specific alert? We are introducing a new concept of ‘Alert Assignee’ – You can assign a specific trigger to a user in the system. Please let us know if you would like to join the beta for this feature.

🗃 Improvements

  • We’re launching a revamped Mixpanel collector. Documentation can be found here.
  • We’ve upgraded our Facebook collectors to work with the latest and greatest libraries.
  • You can now provide feedback from PagerDuty alerts.
  • We’ve added data transformation support to the Observium agent.
  • We’ve created a new version of the Sage agent to support V3.0 metrics.
  • We enabled password encryption as part of agents configuration.

🛠 Bug Fixes

  • We fixed an issue where the link copied from the Triage screen was not working.
  • We fixed a nasty issue where alerts with composites create faulty metrics upon creation.
  • We fixed an issue with Influencing Metrics where the alert editor failed to retrieved the metric name.
  • We fixed an issue which caused ‘testing’ OpsGenie channels to fail.
  • We fixed an issue where agents with milliseconds timestamps would cause a json parsing error.
  • We fixed an issue where the graphs show different units in the metric search vs the simulator. How annoying is that?

🌍 As usual – All the release features, beta features, upcoming features and all your feature requests can be found in our Product Portal. 

What’s New for January 5th

  • User Experience
  • APIs
  • Bug Fixes

Welcome back! A new year begins and with it new years’ resolutions. Our main resolution – keep on delivering new capabilities to bring you value 🥁

🎁 No More Multiple emails!

For those of you who have multiple Anodot accounts (you know who you are 😉) we’ve made a major change – you can now use the same email address for several accounts. The rationale behind this is actually to improve security and prevent ’email harvesting’. You can read all about it here.

🗃 Improvements

  • We’ve fixed the ‘Acknowledge’ APIs which were failing in some situations as well as added a ‘history’ endpoint for the Forecast APIs.
  • A new composite Function – CountZeros will count the number of zeros in a time series. See details here.
  • You are now able to define custom HTTP headers when defining new JIRA channels.
  • We’ve improved the way ‘edit’ actions are being displayed in the Activity Log.
  • We’ve improved the documentation for configuring timezones for Agents.
  • We’ve added better handling for negative numbers in File Agents.
  • We’ve added a new type of service_usage metric to your accounts – feedbacks. Which means you can track how many feedback were given in your account for a given timeframe.

🛠 Bug Fixes

  • We fixed an issue with the link between alerts and dashboards tiles. Did you know that creating an alert from a dashboard tile is considered best practice?
  • Some minor improvements in the design of the dashboard tiles.
  • We fixed an issue with charts not being refreshed when using Influencing Metrics.
  • We fixed an issue which caused some channels to fail being created.

🌍 As usual – All the release features, beta features, upcoming features and all your feature requests can be found in our Product Portal. 

What’s New for December 22nd

  • User Experience
  • Bug Fixes
  • Dashboards

🎄🎄 This is our last update for this year. We wish you and yours a quiet, healthy and peaceful holiday season.
Hope you get some well deserved rest while Anodot works behind the scenes to enable you to relax with your loved ones! 

🎁 Anodot OnPrem Release 4.0

A special delivery from the north pole – we are happy to announce that Anodot OnPrem Release 4.0 is out there and ready for use. You can find the release notes here – https://support.anodot.com/hc/en-us/articles/4411846130578-What-s-New-in-Version-4-0-

🗃 Improvements

  • We’ve updated the colors for the different alert severities. Why would we do such a thing you may ask? Well, we did it so that the colors are now much more evident in the new Severity View of the alert console. This view enables you to sort alert triggers according to severity and not according to the time in which they were created.
  • As you may have noticed,  Anodot has a Labels concept – you can assign labels to dashboards and you can assign them to Alerts. Until recently – these were two completely different sets of labels. We went ahead and merged them – So you can reuse these labels across Anodot.
  • {BETA} We are adding a new capability to fill missing data points in streams. With this capability, are are able to define the ‘filler’ value (usually 0) so that you will not get a ‘No Data’ alert when no value is actually acceptable.
  • We’ve finished the revamp of our ‘expression builder’, used in Metric Search, Dashboard tiles, etc. We hope you appreciate the usability improvements. Learn more here.
  • We’ve added additional dimensions to our Cacti  collector 🌵
  • We now enable you to ‘ungroup’ alerts sent using Jira Channel. This enables getting a different Jira ticket for each metric.

🛠 Bug Fixes

  • We fixed various issues with the design of dashboard tiles.
  • We fixed an issue where agent periodic updates created an audit log entry even tough there was no actual change.
  • We fixed an issue with dashboard filters showing user id instead of name.
  • We fixed an issue with the way several integrations were displayed in the integrations catalog.
  • We’ve improved the way events are organized in the Audit log
  • We fixed a couple of issues in the alert simulation which caused it to disappear when you really really need it.
  • We’ve fixed an issue in the email channel which caused the email list to go missing.
  • Fixed some discrepancies in the way events are displayed in the alert editor.

🌍 As usual – All the release features, beta features, upcoming features and all your feature requests can be found in our Product Portal. 

🚨Update on the Log4j2 vulnerability (CVE-2021-44228)

Dear Customers,

As you may have heard, in the past few days a major vulnerability has been discovered in a key open source library called Log4j2. For a more detailed explanation on the vulnerability – we recommend this great blog by Cloudflare.

We wanted to update all of you that Anodot is completely safe from this vulnerability – we’ve reviewed all our code and production systems thoroughly and we are certain we are not affected by this. We will continue to monitor the situation as it evolves and update you if there are any changes. 

If you have any questions or concerns about this – please reach out directly to product@anodot.com or security@anodot.com.

 

Yours,

The Anodot Team. 

What’s New for December 1st

  • User Experience
  • APIs
  • Bug Fixes

🗃 Improvements

  • We’ve improved the format of the OpsGenie emails we are sending. In general – we are contemplating a major OpsGenie (and PagerDuty) overhaul. Interested? Talk to us.
  • It took us a while, but service usage metrics are now coming to our customers in Frankfurt.
  • A new API Get Groups enables you to get all the groups defined in the account. Documentation is here.
  • We’ve removed the limitation on the number of metrics returned from the Triggered Alerts API.
  • We made some UX improvements to ‘bulk edit’ across the product to make it more usable.
  • Major improvements to the performance of the correlations tab in the new Triage screen.
  • We added a new “clear all” in dashboard dropdowns.
  • A small but super fun improvement to dashboards – “show in metric explorer” is now available from a tile menu.
  • A brand new version of the Grafana Plugin (version 4.0) which includes a major upgrade to how we store authorizations – enabling multiple users to work on the same Anodot plugins even if they are not Grafana Admins.
  • We’ve improved the UX of the “Set owner” dialog for pipelines. Setting an owner to a pipeline makes sure that owner is notified whenever something is wrong with the pipeline. So make sure you do it!

🛠 Bug Fixes

  • We fixed a small (yet annoying) bug in the recipient list of the Alert editor.
  • We fixed an issue with the collection interval of the Segment collector.
  • We fixed a bug in the metric explorer which didn’t allow you to select dates before 2020. Yeah, we are not all millennials.
  • We fixed an issue with gauge tiles in the dashboards.

🌍 As usual – All the release features, beta features, upcoming features and all your feature requests can be found in our Product Portal. 

What’s New for November 21st

  • User Experience
  • Data Collection
  • APIs
  • Bug Fixes

🎁 Integrations Updates

  • We have a brand new B2C Marketing Analytics capability, as part of our partnership with the good people at Rivery. Read all about it here.
  • For all your Prometheus fans out there, we now support using PromQL in certain agents.
  • A new Observium agent has been released to the wild. Documentation can be found here

🗃 Improvements

  • We’ve done some improvements of both the Oracle and Zabbix agents, In addition to the Parquet collector data source definition.
  • Not sure you’ve noticed, but we are slowly improving the usability of the ‘expression builder’ – this is the component which enables you to create an expression based on metrics. The same component is used when creating alerts, dashboard tiles and in the metric explorer. Based on your feedback, we are working to streamline the user experience of using it.
  • For all of you who want to map which streams have which alerts, dashboards and composites mapped to them, our new /totals API provides this information. Documentation is here
  • Feedback API now returns the score and the alertGroup of the anomaly for which the feedback was given. Documentation is here
  • We’ve improved the Facebook Ads Collector – added report level as a dimension.
  • When using Role Based Access (RBAC) – You can now secure channels as well as the data sources.
  • Channels page now support bulk actions. Huzzah!

🛠 Bug Fixes

  • We fixed an issue in the webhook API which caused invalid JSON values.
  • We fixed an issue where you would get (false) No-Data alerts on deleted composites.
  • We fixed an issue with the Datadog collector which caused exceptions because of unstructured tags.
  • We fixed an issue with the alert simulation as well as with applying functions on influencing metrics.
  • We fixed an issue where one of the time frames was missing in the Grafana topology panel.
  • We fixed some issues which happened when moving between the metrics explorer to the dashboard.
  • We fixed a lot of issues in the new triage page.
  • We invested in much better error messages when creating channels.
  • Last but not least – we fixed a very elusive issue where a closed anomaly still showed up as ‘open’ in the alert console in case of a direction change. This one was our nemesis bug for a while now and we are both relieved and thrilled to put it to rest.

🌍  As usual – All the release features, beta features, upcoming features and all your feature requests can be found in our Product Portal. 

What’s New for November 3rd

  • User Experience
  • Data Collection
  • APIs
  • Bug Fixes

🎃 Trick or Treat!

We hope you’ve enjoyed our Halloween theme. The theme was actually the result of our annual R&D Hackathon. There are five other projects from that Hackathon which will make their way to production in the next weeks. That being said – Are you ready for the Shopping period of the year? Have you fine tuned your alerts?

🎁 Integrations Updates

  • Facebook Ads Collector – Now supports asynchronous calls to Facebook’s API. Or is it Meta API? This is so confusing.
  • Our “System Notifications” emails have been expanded to report errors on agent based pipelines in addition to the regular streams.

🗃 Improvements

  • Our Triage screen has now been opened to brave customers. Based on their feedback we have been doing many UX improvements. Have you joined the beta yet?
  • A major new functionality in Grafana – You can now use Grafana variables to filter all the Anodot panels in a dashboard. You need to upgrade your data plugin to V.3.0.1 and your panel plugin to v.1.0.6 and you can get the new functionality.
  • Another improvement to Grafana – We’ve added the option to use “Not” when searching for dimensions in the metrics panel.
  • Channel Management page now shows “Last Modified” for channels (You will need to actually modify a channel for the date to show up).
  • We’ve improved the way Influencing metrics are presented in the details tab of the Alert Manager.
  • Alerts which were created from dashboards will now show with a “Go to dashboard” button in the new slack application.
  • We’ve updated our Forecast APIs to make it easier to retrieve forecast results regardless of the forecast tasks. Documentation is here.

🛠 Bug Fixes

  • We fixed an issue where you were not able to create a dashboard tile from the metric explorer as well as the expression builder becoming un-editable when switching from the dashboard to the metric explorer.
  • We fixed the behavior of the ‘Show composite’ toggle in the expression builder of dashboard tiles.
  • We fixed the way Business Impact was formatted in Microsoft Teams alerts
  • An issue in Grafana where clicking on the “function” button erases the dimensions / sorting was fixed.
  • We fixed a minor issue in the alert summary tab where long error texts would overlap with other elements of the tab.

🌍 As usual – All the release features, beta features, upcoming features and all your feature requests can be found in our Product Portal. 

What’s New for October 20th

  • User Experience
  • Data Collection
  • Alerts Improvements
  • Bug Fixes
  • Dashboards

Have you seen our quarterly product update? We had some massive new features announced there. That being said – its time to move on and resume our bi-weekly cadence of updates. So here goes:

🎁 Integrations Updates

This month we are doubling down on APM! Two of the major APM (Application Performance Monitoring) tools have new collectors released:

  • NewRelic Collector – A new collector for getting metrics out of NewRelic. Details can be found here.
  • DataDog Collector – A new collector for getting metrics out of DataDog . Details can be found here.
  • In addition, We’ve made improvements in the error handling of the S3 Parquet collector.

🥧 The one thing better than Apple Pie?

It has to be the new Pie tile in Anodot Dashboards. We were going to wait until March 14th, but its ready now – the new Pie Tile!

What’s New for October 20th

The new tile is a great way to view distribution of metrics based on specific dimension value:

What’s New for October 20th

The new tile is available only in the new dashboards. Have you migrated yours already?

🗃 Improvements

  • We’ve overhauled our Microsoft Teams channel. This overhaul includes an improved look and feel, but also support for Actions and Impact. We’ve also improved the explanations you get when an alert is closed.
  • We’ve added Actions support for Opsgenie channel and made links open in a new tab.
  • We’ve made some improvements to our seasonality detection to take into account outliers in the data as well as improved the time it reacted to ‘change points’. We’ve just made the best detection algorithms in the industry even better!

🛠 Bug Fixes

  • We fixed an issue in the users list for Admins where the “Last Active” value was occasionally incorrect.
  • We fixed an issue in the dashboards where duplicating a dashboard with a different owner would fail.
  • We fixed an issue in the Activity log where the ‘Groups’ wasn’t working correctly.

🌍 As usual – All the release features, beta features, upcoming features and all your feature requests can be found in our Product Portal.