Friendly Error Messages (3.0)

Most common issues

No.	Message	Root cause	Possible Solution
1.	No connection string or instrumentation key provided	User didnot provide the connection string in config.	User has to provide connection string in config.
2.	ApplicationInsights Java Agent failed to connect to CdsProfiler end point. Unable to find valid certification path to requested target.	Customer probably using a custom Java keystore.	Customer might need to import the Application Insights endpoint SSL certificates into their Java Keystore.
3.	ApplicationInsights Java Agent failed to connect to Live metric end point. Unable to find valid certification path to requested target.	Customer probably using a custom Java keystore.	Customer might need to import the Application Insights Live Metric endpoint("https://rt.services.visualstudio.com") SSL certificates into their Java Keystore.
4.	ApplicationInsights Java Agent failed to send telemetry data. Unable to find valid certification path to requested target.	Customer probably using a custom Java keystore.	Customer might need to import the Application Insights endpoint SSL certificates into their Java Keystore.
5.	ApplicationInsights Java Agent failed to connect to CdsProfiler end point. Unable to find valid certification path to requested target.	Customer probably using a custom Java keystore.	Customer might need to import the Application Insights endpoint SSL certificates into their Java Keystore.

Telemetry processors related issues

No.	Message	Root cause	Possible Solution
1.	Telemetry processor configuration does not have valid regex: <user provided regex>	User did not provide a valid regex in telemetry processor config	User has to provide a valid regex in config.
2.	Telemetry processor configuration has a processor with no type!!!	User provided a telemetry processor config without a processor type	Processor type is mandatory when using telemetry processors.
3.	Telemetry processor configuration has invalid attribute processor configuration with empty actions!!!	User has provided a telemetry processor config without actions or empty actions	Telemetry processor actions should have a valid action and key
4.	Telemetry processor configuration has invalid span/log processor configuration with empty name object!!!	User has provided a span/log processor config with no name object	Span/Log processors should have a valid name object.
5.	Telemetry processor configuration has invalid name object with no fromAttributes or no toAttributes!!!	Span/Log processor donot have fromAttributes or toAttributes object in the config.	User has to provide at least one of fromAttributes or toAttributes in the Span/log processor configuration.
6.	Telemetry processor configuration has invalid toAttribute value with no rules!!!.	Span/Log processor has a toAttribute object with no list of rules	User has to provide atleast one rule in the toAttribute object of processor configuration.
7.	Telemetry processor configuration has invalid include/exclude value with no matchType!!!	A include/exclude object of processor config is missing matchType	User has to provide a valid matchType in the include/exclude object of processor config
8.	Telemetry processor configuration has invalid include/exclude value with attribute which has empty key!!!	A include/exclude object of processor config is missing a valid key	key with a valid value is mandatory for a include/exclude object of processor config
9.	Telemetry processor configuration has invalid include/exclude value with no spanNames or no attributes!!!	A valid include/exclude object of span/attribute processor config should have at least one of spanNames or attributes	User has to provide spanNames or attributes or both in the include/exclude object.
10.	Telemetry processor configuration has invalid include/exclude value with no logNames or no attributes!!!	A valid include/exclude object of log processor config should have at least one of logNames or attributes	User has to provide logNames or attributes or both in the include/exclude object.
11.	Telemetry processor configuration does not have valid regex to extract attributes:<user provided regex>	User did not provide a valid regex in the pattern value of the extract action object.	User has to provide a valid regex of the form (?<name>X) where 'X' is the usual regular expression.
12.	Telemetry processor configuration has invalid action with empty key!!!	User provided config has an action object with no key	A valid non empty key has to be provided for every action object.
13.	Telemetry processor configuration has invalid action with empty value or empty fromAttribute!!!	User provided config has an action object with no value or fromAttribute	User has to provide either one of non empty value or non empty fromAttribute for every action object of type insert or update
14.	Telemetry processor configuration has invalid action with empty pattern!!!	User provided config has an action object of type extract with no pattern	User has to provide a valied pattern for every action object of type extract