Splunk AppDynamics

Import Health Rule error message - Unexpected character (- (code 45)) in numeric value

Mikel_Osinalde_
Path Finder

Hi everyone,

Has anyone faced the following problem when importing a health rule in JSON format?

I'm using the following curl command:

curl -sL -w "%{http_code}" -X POST --user "${USER}:${PASS}" \
-H "Content-Type: application/json" -F file=@${FILE}.json \
https://$HOST/controller/alerting/rest/v1/applications/$APP_ID/health-rules

which in every JSON file I tried, returns me this error:

{
"statusCode" : 400,
"message" : "Unexpected character (- (code 45)) in numeric value: expected digit (0-9) to follow minus sign, for valid numeric value "
}

... even if I'm using the same JSON as in the official documentation:

https://docs.appdynamics.com/display/PRO45/Health+Rule+API

The JSON files I've tried do not contain any hyphen characters, so apparently the request payload is not related to the error cause.

Anyone been there?

Thanks and regards.

Labels (3)
Tags (2)
0 Karma
1 Solution

Morelz
Motivator

Hi there

Can you share your health rule json file you are trying to import?

Did you build it from scratch, or did you export it, and you are trying to import it again?

The query you should be using is as follows

Need to use --data, not -F File

curl -X POST --user user@user:password "https://<controller details/controller/alerting/rest/v1/applications/<application ID>/health-rules" -H "Content-Type: application/json" --data "@test2.json"

View solution in original post

Morelz
Motivator

Hi there

Can you share your health rule json file you are trying to import?

Did you build it from scratch, or did you export it, and you are trying to import it again?

The query you should be using is as follows

Need to use --data, not -F File

curl -X POST --user user@user:password "https://<controller details/controller/alerting/rest/v1/applications/<application ID>/health-rules" -H "Content-Type: application/json" --data "@test2.json"

Mikel_Osinalde_
Path Finder

Good morning Mario,

Thanks for your tip, once I changed to --data instead of -F file, it worked!!!

Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Agentic SOC Triage: Investigating Splunk ES Notables with MCP Server and a Local LLM

The Problem: Too Many Alerts, Too Little Context Security operations teams running Splunk Enterprise Security ...

All Work and No Play? Not at .conf26! Unwind at These Evening Events

Between hands-on technical sessions, keynote reveals, and diving into live architectures, .conf26 is packed ...

Join the Hackathon at .conf26 and build a No-Code AI agent

Join us for the AI Agent Buildathon, an in-person, three-hour hands-on Hackathon where you’ll use Splunk Agent ...