Closed that1guy closed 9 years ago
Now have this running properly in the staging environment in a container...
NOTE: The URL below will only work if you add your IP to the security group "Staging App" in AWS.
http://52.11.249.169:8884/v1/status
{
"anchors": {
"averageRequestTime": 2954.6111111111113,
"totalErrorCount": 35,
"totalRequestCount": 36,
"totalRequestTime": 106366
},
"polling": {
"averageRequestTime": 2104,
"totalErrorCount": 0,
"totalRequestCount": 1,
"totalRequestTime": 2104
},
"postings": {
"averagePostingCount": 15,
"averageSaveTime": 4088,
"totalErrorCount": 0,
"totalPostingCount": 15,
"totalSaveCount": 1,
"totalSaveTime": 4088
},
"schedule": {
"interval": "every 30 secs",
"totalRunCount": 36
}
}
Also, turns out that this had to do with how the hashtagsell/docker-build script staging-posting-sync-ca.sh
was configured - it used US-CA
instead of USA-CA
.
Assigning back to @that1guy to verify locally - this issue pertains to the agent not working in a local environment. Please be sure to git pull as well to have the latest code and if the issue is reproduced, please post the configuration used.
Things are now running great on my local machine. So well in fact that I'm concerned something may not be running correctly in cloud. Here is my config file on my local machine.
{
"logging": {
"level": "trace"
},
"models": {
"postings": {
"schedule": {
"interval": "every 30 secs"
},
"polling" : {
"location": {
"state": "USA-CA"
}
}
}
},
"services": {
"3taps": {
"apikey": "f2862071ede0bbd93bee4f091c522a9e"
},
"postings": {
"url": "http://localhost:4043/v1/postings"
}
}
}
{
"anchors": {
"averageRequestTime": 2305.9583333333335,
"totalErrorCount": 51,
"totalRequestCount": 72,
"totalRequestTime": 166029
},
"polling": {
"averageRequestTime": 1561.3333333333333,
"totalErrorCount": 0,
"totalRequestCount": 24,
"totalRequestTime": 37472
},
"postings": {
"averagePostingCount": 5.476190476190476,
"averageSaveTime": 3002.285714285714,
"totalErrorCount": 8,
"totalPostingCount": 115,
"totalSaveCount": 21,
"totalSaveTime": 63048
},
"schedule": {
"interval": "every 30 secs",
"totalRunCount": 74
}
}
Why are the status details @ http://52.11.249.169:8884/v1/status indicating we've only had total save count of 3?
{
"anchors": {
"averageRequestTime": 3100.6744585768306,
"totalErrorCount": 5815,
"totalRequestCount": 5818,
"totalRequestTime": 18039724
},
"polling": {
"averageRequestTime": 4201,
"totalErrorCount": 0,
"totalRequestCount": 3,
"totalRequestTime": 12603
},
"postings": {
"averagePostingCount": 5,
"averageSaveTime": 8053.333333333333,
"totalErrorCount": 2,
"totalPostingCount": 15,
"totalSaveCount": 3,
"totalSaveTime": 24160
},
"schedule": {
"interval": "every 30 secs",
"totalRunCount": 5818
}
}
FYI between 1:32p and 1:45p I've ingested approx 5000 items on my local machine.. just to put things in perspective.
Not relevant to today's issues.
On my local machine sync agent never seems to bring any postings down.
config file
Node logs showing no postings found
However if I manually look up the anchors content via URL I see 3Taps is giving results.
Excerpt of 3Taps response from manual URL