New Countly Install!

Greetings Guys,

We've installed the lasted version of Countly Community Edition v18.04.1 and has set up an application within the dashboard and haven't been able to track or gather any data regarding that app. Has anyone encountered this issue with Countly Community Edition v18.04.1 and if so, what solutions you used to resolve the issue.

Thanks in advance

0

Comments

12 comments
  • Hello,
    in Countly SDK in your app, enable logging, to check what SDK does and do requests succeed.

    If they succeed, then try on Countly dashboard, Management -> Event Logs to check if there are requests from SDK registered for your app.

    Usual problem is using app_id or api_key instead of require app_key for SDK

    0
    Comment actions Permalink
  • Thanks for the quick response. I used the word app due to how everything shows up in the countly dashboard, but this is a website and we added the Web SDK code to the website. We used all the "CHOOSE FROM WHERE TO LOAD THE SCRIPT" configurations without any success.

    Checked the "Event Logs" and there's nothing showing there.

    0
    Comment actions Permalink
  • ok, so add debug option in Countly Web SDK and check browser console for output

    0
    Comment actions Permalink
  • Greetings Ar2rsawseen,

    We've installed Countly Community Edition v18.08.1 on a new install of ubuntu server 16.04.4 and currently have the Countly service running but we're not able to track an traffic coming from the website we've. The website is running on Wordpress and we used the web integration to add the script to the website. Can you please help use resolve this issue we currently have with trying to track our traffic to our site?
    32%20AM
    19%20AM
    17%20AM
    Thanks in advance
    Fred Turner

    0
    Comment actions Permalink
  • Hello,
    to report data from Wordpress to Countly, users who access Wordpress site must be able to communicate to Countly server.
    From your snippet I see that you use as address: 192.168.1.76, which seems to be like an internal server address, and it would not be accessible for others outside your network.

    So you must have some external IP address with which to access Countly server (like access Countly dashboard) from outside of your internal network. And you should use that when creating snippet for Countly code or using it with integration in Wordpress plugin.

    0
    Comment actions Permalink
  • Greetings Guys,

    We've installed the lasted version of Countly Community Edition v18.08.2 52%20AM on a DigitalOcean droplet (2GB / 50GB Disk - Ubuntu 16.04.4 x64) 28%20AM and has set up an wep application within the dashboard and haven't been able to track or gather any data regarding the website traffic. Has anyone encountered this issue with Countly Community Edition v18.08.2 and if so, what solutions you used to resolve the issue.

    Thanks in advance

    0
    Comment actions Permalink
  • Hello,
    so debug such cases usually involves

    1. Enable debug logging in SDK
      Check if requests are being made
      Check if they fail or are successfully sent to server

    If all seems ok

    1. Check if SDK requests are arriving to server
      Check under Management -> Event Logs
      Check if there are any errors/problems displayed there with your requests there

    If all seems ok

    1. Check server for errors
      Check countly/log/countly-api.log for errors
    0
    Comment actions Permalink
  • I found a few errors but not clear on what's causing the issue.

    2018-11-28T14:49:48.531Z: ERROR [db:read] Error reading systemlogs {"name":"find","args":[null]} MongoError: bad sort specification {"name":"MongoError","message":"bad sort specification","ok":0,"errmsg":"bad sort specification","code":2,"codeName":"BadValue"}
    { MongoError: bad sort specification
    at queryCallback (/root/countly/node_modules/mongodb-core/lib/cursor.js:247:25)
    at /root/countly/node_modules/mongodb-core/lib/connection/pool.js:531:18
    at _combinedTickCallback (internal/process/next_tick.js:132:7)
    at process._tickCallback (internal/process/next_tick.js:181:9)
    name: 'MongoError',
    message: 'bad sort specification',
    ok: 0,
    errmsg: 'bad sort specification',
    code: 2,
    codeName: 'BadValue',
    [Symbol(mongoErrorContextSymbol)]: {} }
    2018-11-28T14:49:58.162Z: ERROR [db:read] Error reading systemlogs {"name":"find","args":[null]} MongoError: bad sort specification {"name":"MongoError","message":"bad sort specification","ok":0,"errmsg":"bad sort specification","code":2,"codeName":"BadValue"}
    { MongoError: bad sort specification
    at queryCallback (/root/countly/node_modules/mongodb-core/lib/cursor.js:247:25)
    at /root/countly/node_modules/mongodb-core/lib/connection/pool.js:531:18
    at _combinedTickCallback (internal/process/next_tick.js:132:7)
    at process._tickCallback (internal/process/next_tick.js:181:9)
    name: 'MongoError',
    message: 'bad sort specification',
    ok: 0,
    errmsg: 'bad sort specification',
    code: 2,
    codeName: 'BadValue',
    [Symbol(mongoErrorContextSymbol)]: {} }

    0
    Comment actions Permalink
  • Nope, that is not related.
    Start with first step please

    0
    Comment actions Permalink
  • Greetings Ar2rsawseen,

    We were finally able to get Countly Community to work, but have another issue that's happening now that it's working.

    We have a number of different devices that we use to test if Countly is tracking correctly. Screen%20Shot%207 Screen%20Shot%206

    We understand that Countly tracks each device as one visitor, but also tracks the sessions of that one visitor/device. So that means each time one of our devices visits the website a new session should be logged in the database and recorded on the dashboard under Total Session.

    But that's not the case because something within our Countly Community Server isn't recording all our devices or the device sessions.
    Screen%20Shot%201 Screen%20Shot%202

    We're using the Countly Wordpress Plugin on our site and has added the correct information to track all the traffic reaching our site.

    Screen%20Shot%205

    As you can see it's only recorded just 5 of our devices Id's and only 6 sessions, which is totally wrong becaused we used all our devices to see if Countly was recording everything correctly before we start adding events to track different actions on the site.

    Screen%20Shot%204

    I'm also attaching a screenshot of the server logs for your viewing.

    Screen%20Shot%203

    We've been using Countly Community Edition since 2015 have never encountered anything like this, Please help us resolve these issues.

    Thanks in advance.

    0
    Comment actions Permalink
  • Sorry, I was sick for the most of the week, only now getting better
    But unfortunately I can't see screenshots anymore, @gorkem do screenshots have expiration time?

    Unfortunately it seems to be related to similar problem you stated before about SDK not reaching server?
    What was the issue previous time?
    Maybe there is a specific pattern ? Specific devices cannot reach server or Web SDK breaks in those devices?

    0
    Comment actions Permalink
  • That is weird, I can see other images but not the ones here. Maybe Fred removed or something different. I will keep an eye and check for issues Discourse may have.

    0
    Comment actions Permalink

Please sign in to leave a comment.