Carbon Core Release Notes: Carboncore Framework Release Note

Posted : admin On 18.06.2019
Carbon Core Release Notes: Carboncore Framework Release Note Average ratng: 6,0/10 7824 reviews

Download URLs Download the appropriate release for your New Relic.NET agent: Fixes. Fixes a bug in SQL-related database instrumentation that potentially causes a CPU spike. This bug appeared in the Agent version 8.9.130. New Features.NET Core Adds support for.NET Core 2.2 Preview 3. Adds support for Asp.NET Core 2.2 Preview 3.

ISF1P195K_CORE_LIB_RELEASE_RN Release Notes Rev 1.0, 2/2014 Release Notes for Xtrinsic. This is the Xtrinsic Intelligent Sensor Framework (ISF) release by Freescale Semiconductor. It targets the Freescale Xtrinsic FXLC95000CL Intelligent, Motion-Sensing Platform. Home London Release Notes London release notes Features and changes by product Now Platform release notes Automated Test Framework release notes. All versions. Core Configuration. Currency fields. Data Management. Form Administration. Carbon Black integration.

Improves the performance of Cross Application Tracing. Upgrading. Follow standard procedures to. If you are upgrading from a particularly old agent, review the list of major changes and procedures to. Fixes. Fixes potential memory leak when Distributed Tracing is enabled.

Carbon core release notes: carbon core framework release notebook

Fixes an issue where a NullReferenceException is logged for certain data stores (MongoDB and Couchbase) when distributed tracing is enabled. Fixes an issue where a transaction start time is incorrect when an error has been reported. Other Information. After November 7th, 2018 the Core20 directory will be removed from the download site.

This folder currently contains an outdated version of the.Net Core agent. The most up-to-date version of the.NET Core agent can be found in in latestrelease directory. Upgrading. Follow standard procedures to.

If you are upgrading from a particularly old agent, review the list of major changes and procedures to. New Features.

Users can now set a customized host name to be displayed in the APM UI via the newrelic.config file or an environment variable. For more information, visit.NET Framework Added the ability to enable the agent from the local newrelic.config file for all non-IIS hosted.NET Framework applications. Additional information can be found at: Fixes. The profiler now honors the log level configuration setting that is set in the app-local newrelic.config file. Other Information. After November 7th, 2018 the Core20 directory will be removed from the download site. This folder currently contains an outdated version of the.Net Core agent.

The most up-to-date version of the.NET Core agent can be found in in latestrelease directory. Upgrading. Follow standard procedures to. If you are upgrading from a particularly old agent, review the list of major changes and procedures to. New Features.

Distributed tracing lets you see the path that a request takes as it travels through your distributed system. By showing the distributed activity through a unified view, you can troubleshoot and understand a complex system better than ever before. Distributed tracing is available with an APM Pro or equivalent subscription. To see a complete distributed trace, you need to enable the feature on a set of neighboring services. Enabling distributed tracing changes the behavior of some New Relic features, so carefully consult the before you enable this feature. To enable distributed tracing, see. Upgrading.

Follow standard procedures to. If you are upgrading from a particularly old agent, review the list of major changes and procedures to.

New Features. Adds support for capturing request.uri attribute for WCF services when available.NET Core SQL query parameter values can now be captured on Slow SQL Traces on Linux. Fixes. Fixes an issue where errors set to be ignored through configuration were not being ignored.

Fixes an issue where running the thread profiler can cause an application to terminate. Fixes an issue where transaction events could be dropped.NET Core Fixes an issue for.NET Core applications running on Linux when serializing slow SQL trace and explain plan data for transmission to New Relic. Previously, the following exception would be seen in the agent logs: NewRelic ERROR: System.PlatformNotSupportedException: Operation is not supported on this platform. Notes. We will be removing the core20 directory from the download site the week of September 3rd, 2018 as it contains a deprecated version of the.Net Core agent. Please be sure to update any of your scripts that reference this location accordingly.

All downloads for the current version of the agent can be found in the latestrelease directory on the download site. Historical versions can be found in the previousreleases directory.

Upgrading. Follow standard procedures to. If you are upgrading from a particularly old agent, review the list of major changes and procedures to. Download URLs Download the appropriate release for your New Relic.NET agent: New Features.

SQL query parameter values can now be captured on Slow SQL Traces. This feature can be enabled with the new configuration option datastoreTracer.queryParameters.

The transactionTracer.recordsql configuration option must also be set to raw. See documentation.

This feature should be used with caution as it can lead to the capture of sensitive data. High Security Mode prevents the use of this feature. Windows support only.

Linux support coming soon.NET Framework Adds support for tracking async transactions when.ConfigureAwait(false) is used from async controller actions in ASP.NET MVC applications.NET Core Adds support for.NET Core 2.1. Support for.NET Core 2.1 requires at least CLR version 2.1.3 and tiered compilation must not be enabled. Fixes.NET Core Fixes issue where status code based errors would be reported instead of the actual noticed Exception. This most commonly occurred with errors noticed in the ExceptionHandlerMiddleware (app.UseExceptionHandler(.)). Fixes an issue where only the first request parameter is captured when request.parameters. attributes are added to an include list. Notes.

We will be removing the core20 directory from the download site the week of September 3rd, 2018 as it contains a deprecated version of the.Net Core agent. Please be sure to update any of your scripts that reference this location accordingly. All downloads for the current version of the agent can be found in the latestrelease directory on the download site. Historical versions can be found in the previousreleases directory.

Upgrading. Follow standard procedures to. If you are upgrading from a particularly old agent, review the list of major changes and procedures to. Download URLs Download the appropriate release for your New Relic.NET agent: New Features. Adds automatic capture of datastore information for MongoDB driver versions 2.6.x, 2.5.x, 2.4.x, and 2.3.x.NET Core 2.0 Adds thread profiler support for.NET Core applications running on Windows. Fixes. Improved the agent's ability to recover from certain connection related issues without requiring an agent or application restart.

Upgrading. Follow standard procedures to.

If you are upgrading from a particularly old agent, review the list of major changes and procedures to. Download URLs Download the appropriate release for your New Relic.NET agent: New Features. Replaces the requesturi attribute with request.uri. Adds the request.uri attribute to transaction traces and error traces. If you wish to control the presence of this attribute please follow the instructions at Fixes.NET Framework Fixes issue of recursive directory creation when recovering from a failed upgrade install in the scriptable installer.NET Framework Fixes issue where Thread Profiler fails to resolve types and method names.

These would appear as UnknownClass.UnknownMethod in a profile. Upgrading.

Follow standard procedures to. If you are upgrading from a particularly old agent, review the list of major changes and procedures to. New Features.NET Framework The.NET Framework agent now supports instrumenting ASP.NET Core applications that are running on.NET Framework. The.NET Core specific agent is still required for instrumenting applications running on.NET Core. Fixes.

Fixed issue where deadlocks could occur in some situations when a ThreadAbortException was thrown within a client application. Fixed issue where only the first transaction name set via API call to SetTransactionName would be honored. Now, the last call to SetTransactionName will be the name applied to the transaction.NET Core 2.0 Fixed issue with the.NET Core agent on Windows where the CORECLRPROFILERPATH environment variable was not being expanded properly in certain deployment scenarios.NET Framework Fixed issue introduced in agent version 8.1.709.0 that caused some.NET Framework applications to throw the following exception: Unhandled Exception: System.IO.FileNotFoundException: Could not load file or assembly 'netstandard, Version=2.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies. Upgrading. Follow standard procedures to. If you are upgrading from a particularly old agent, review the list of major changes and procedures to. This release has been unpublished.

Use version or higher. Planex communications inc. cqw-mr500 free driver. This version introduced a bug that could cause crashes for.NET Framework applications manually loading types from assemblies in the application domain. This includes enumerating custom attributes.

The encountered error will appear like the following: Unhandled Exception: System.IO.FileNotFoundException: Could not load file or assembly 'netstandard, Version=2.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies. The system cannot find the file specified New Features.NET Framework The.NET Framework agent now supports instrumenting ASP.NET Core applications that are running on.NET Framework.

The.NET Core specific agent is still required for instrumenting applications running on.NET Core. Fixes.

Fixed issue where deadlocks could occur in some situations when a ThreadAbortException was thrown within a client application. Fixed issue where only the first transaction name set via API call to SetTransactionName would be honored. Now, the last call to SetTransactionName will be the name applied to the transaction.NET Core 2.0 Fixed issue with the.NET Core agent on Windows where the CORECLRPROFILERPATH environment variable was not being expanded properly in certain deployment scenarios. Upgrading. Follow standard procedures to. If you are upgrading from a particularly old agent, review the list of major changes and procedures to. New Features.

Adds stripExceptionMessages configuration option to the newrelic.config file. When enabled, this will remove error messages from errors that are reported to New Relic. This is the same behavior as having High Security Mode enabled but can be used without High Security Mode. The default value for this setting is false.

Carbon Core Release Notes: Carbon Core Framework Release Notebook

Fixes. Security Bulletin: The agent will no longer run explain plans on MySQL queries that have multiple statements. Other Changes. In order to increase security, disabling agent HTTPS communication via the service SSL configuration is no longer allowed. WCF service parameters are now captured as request.parameters. attributes and are no longer sent as service.request.

attributes. Upgrading. Follow standard procedures to. If you are upgrading from a particularly old agent, review the list of major changes and procedures to. Download URLs Download the appropriate release for your New Relic.NET agent:. This is a security-only release for the 6.x agents that support legacy frameworks (.NET version 4.5 and lower).

Carbon Core Release Notes: Carboncore Framework Release Note

If you are on.NET version 4.5 and higher or.NET Core, the 7.x or later versions of the agent should be used. Fixes. Security Bulletin: The agent will no longer run explain plans on MySQL queries which have multiple statements. Upgrading. Follow standard procedures to. If you are upgrading from a particularly old agent, review the list of major changes and procedures to.

New Features. Improved metadata collection for cloud providers. The agent now collects additional metadata when running in AWS, GCP, and Azure. This information is used to provide an enhanced experience when the agent is deployed on those platforms. Fixes.

Carboncore

Fixed an issue where transactions could be dropped when they included datastore segments and the following exception was logged: NewRelic ERROR: An exception occurred while doing some background work: System.NullReferenceException: Object reference not set to an instance of an object. Fixed an issue where SOAP instrumentation would report System.Reflection.TargetInvocationException errors when a more specific error existed. Inner exceptions will now be reported when they exist. Deprecation Warnings The follow items are considered deprecated and will be removed with the upcoming 8.x major release:. Disabling agent HTTPS communication via the service SSL configuration will no longer be allowed starting in 8.x versions of the agent. WCF service parameters will no longer be sent as service.request.

attributes starting in 8.x versions of the agent. These parameters will be sent in the form request.parameters.

Upgrading. Follow standard procedures to. If you are upgrading from a particularly old agent, review the list of major changes and procedures to. New Features. Modifying custom instrumentation XML files can now be performed without having to restart the monitored application. Instrumentation updates will be applied ‘dynamically’ at runtime. This feature required functionality provided by new APIs introduced in.NET Framework 4.5 and newer, which this release also addresses (see ‘Framework Support’ section below).

Fixes. Security Bulletin: Fixes issue where error messages were not fully being filtered out of error traces and error events when High Security Mode was enabled.

Fixed an issue with automatic browser monitoring which could cause a stack overflow exception. For custom instrumentation, the metricName parameter will be honored without needing to set transactionNamingPriority. The scriptable installer will now successfully install and uninstall in scenarios where there is a space in the path to the installation files. Framework Support. This release of the agent removes support for.NET Framework versions earlier than 4.5. See our about this from November of last year, for more details.

This is not an end of life for the 6.x agents (that support older.NET Frameworks), which will continue to work and report into New Relic. Upgrading. Follow standard procedures to. If you are upgrading from a particularly old agent, review the list of major changes and procedures to. New Features. The request URI for a web transaction will now be included as an attribute of transaction events and error events. The New Relic.NET Status Monitor has been retired and is no longer included in the install.

The replacement tool is. To download the most recent version, select the link in the. Fixes. Security Bulletin: Fixes issue where query parameters were being included in the URL property of transaction trace segments for external calls (uses of System.Net.HttpClient, System.Net.WebRequest, or third-party libraries which are built on top of those).

Query parameters will no longer be included in transaction trace segments. Transaction names will be rolled up for web transactions resulting in a 400 or 500 level HTTP status code and a higher priority name has not been set. This helps prevent. Fixed error that could result in the one time loss of a metric and/or transaction for an instrumentation point at the start of monitoring an application. '.NewRelic ERROR: Tracer invocation error: System.ArgumentException: An item with the same key has already been added. Minor log level adjustments in the profiler logging.

Suppresses benign error Failed to tokenize method signature: class System.Reflection.Assembly System.CannotUnloadAppDomainException::LoadAssemblyOrThrow(string).NET Core 2.0 For.NET Core agent users on Linux, this release fixes a problem with the run.sh convenience script in combination with a custom installation path.NET Framework Fixes issue resulting in SerializationExceptions when using.Net Remoting. Upgrading. Follow standard procedures to. If you are upgrading from a particularly old agent, review the list of major changes and procedures to.

New Relic Agent for.NET Core 2.0 GA Highlights. Windows and Linux support, including Azure App Services and Docker. Automatic instrumentation for ASP.NET Core applications running on Kestrel. External calls via HttpClient. Database instrumentation for System.Data.SqlClient, Npgsql, and MySql.Data. Custom instrumentation via XML and transaction/trace attributes.

NewRelic.Agent.Api support For a more detailed list, see the. The.NET Core 2.0 agent is a separate install and can live side-by-side on the same server as the.NET Framework agent. For installation information, follow the procedures for your operating system as applicable:. New Shared Features. Database instrumentation performance has been improved. Explain plans are no longer captured by default for supported database systems: Microsoft SQL Server and MySQL. Explain plans can be enabled via.

Updating the Agent. Follow standard procedures to. If you are upgrading from a particularly old agent, review the list of major changes and procedures to. New Features.

Adds support for RestSharp library. The Agent can now instrument async and non-async methods from a RestSharp client.

For supported methods, please visit. The application name reported to New Relic APM can now be set by defining the NEWRELICAPPNAME environment variable.

Fixes. Fixed some situations where SerializationException occurs in the agent log file. The injection of Browser Monitor JavaScript directly above the body tag on a page should occur less often. Fixes issue where datastore instance information would not be reported for some NpgsqlCommand async calls. Fixed remaining cases where 9-digit SQL trace identifiers were generated, failing Data Loss Prevention monitors which interpret the value as a Social Security Number. Upgrading. Follow standard procedures to.

If you are upgrading from a particularly old agent, review the list of major changes and procedures to.

Confluence 1.0 Ring the bells. Break out the champagne. Paint the town red. Dance naked in the streets.

Or at least that's what we'll be up to tonight, because we're finally releasing Confluence 1.0! Confluence 1.0 represents the hard work and dedication of quite a few people. Obviously there's the development team: Ara, Armond, Charles, Dave, Mike and Ross, but there's also the JIRA team and the rest of the guys at Altlassian who have offered support, advice, and loud music. A huge thanks also goes out to everyone involved in the beta-testing program. Your real-world use of Confluence gave us invaluable suggestions and bug-reports, and we apologize for the times we've messed up your databases on the way. We're pretty proud of all the cool stuff we've managed to fit into Confluence already, and we're looking forward to making it even better in forthcoming versions (Remember, a license entitles you to a year of upgrades).

The only sad moment for the day is that for the 1.0 release, we had to lose emoticons. The regular expression responsible for turning into a smiley-face was causing pages to take ten seconds to render. Commenting out the filter lowers the rendering time of even highly complex pages to a few hundred milliseconds. We promise, the smileys will return in a future version, faster and stronger than ever! Or if you don't mind the cost, you can re-enable them by uncommenting the emoticonFilter line in wikiSubsystemContext.xml Users of late Release Candidate builds will notice a substantial improvement in performance as a result. Contents.

See also: New Features For once, we managed to resist the urge to add any new features this week, since we were busy cleaning everything up for today's release.