Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Dec 11 19:54
    niemyjski synchronize #452
  • Dec 11 19:54

    niemyjski on elastic7

    Decrease batch size (compare)

  • Dec 11 14:51
    niemyjski synchronize #452
  • Dec 11 14:51

    niemyjski on elastic7

    Reset the alias cache before ru… (compare)

  • Dec 11 04:03

    ejsmith on mappings-refactor

    (compare)

  • Dec 11 04:02
    ejsmith synchronize #452
  • Dec 11 04:02

    ejsmith on elastic7

    Change a bunch of index field s… Updated dependencies. Revert to 2201-pre and 6 more (compare)

  • Dec 11 04:02
    ejsmith closed #470
  • Dec 11 04:02
    ejsmith edited #470
  • Dec 11 03:59
    ejsmith opened #470
  • Dec 11 03:14

    niemyjski on mappings-refactor

    Updated to latest foundatio (compare)

  • Dec 11 02:59

    niemyjski on mappings-refactor

    Tweaked the event index mapping… (compare)

  • Dec 11 01:53

    ejsmith on mappings-refactor

    Update cache client list method… (compare)

  • Dec 11 01:19

    ejsmith on mappings-refactor

    More index work (compare)

  • Dec 10 13:26
    niemyjski commented #468
  • Dec 10 13:26
    niemyjski closed #469
  • Dec 10 13:26
    niemyjski commented #469
  • Dec 10 09:27
    xuyi100200 starred exceptionless/Exceptionless
  • Dec 10 08:55
  • Dec 10 05:34

    ejsmith on mappings-refactor

    Some indexing changes... still … (compare)

Blake Niemyjski
@niemyjski
i'd love to support it
but they sure don't make it easy
Sander Rijken
@srijken
the only thing is.. when a support call comes it that something's broken, it is very useful to be able to see that it's IE8
Blake Niemyjski
@niemyjski
yeah
one thing you could do is just make a json post using our cors client
Sander Rijken
@srijken
yeah
Blake Niemyjski
@niemyjski
it blows and I don't know what to do
usage of ie8 is way down there
google, github, microsoft you name it doesn't support it anymore
Sander Rijken
@srijken
same for us, except for some one or 2 big ones
this one was running XP as well :(
Blake Niemyjski
@niemyjski
tell them to run chrome
:)
:(
windows 7 ships with ie8 but is upgradable to ie latest
Sander Rijken
@srijken
yeah
Blake Niemyjski
@niemyjski
xp -> ie8 (I think) but they can run chrome / firefox
Sander Rijken
@srijken
yeah they should
I think it's better to just advise them to switch/upgrade browsers
Blake Niemyjski
@niemyjski
morning
whats new with you all
Sander Rijken
@srijken
morning :)
or not anymore probably
Blake Niemyjski
@niemyjski
lol nope
Blake Niemyjski
@niemyjski
ah I love clean code
and it's getting cleaner / simpler :D
:D
she builds
Sander Rijken
@srijken
nice :)
Lukas Wöhrl
@woehrl01
Hi! Im using JsonConvert.SerializeObject(error.Target) and new ErrorBuilder(JsonConvert.DeserializeObject<Error>(log)) to Pipe some exceptions from client which don't have an Internet connection. Since my update to 2.x those exceptions are all Grouped to the same stack even so they have different Messages. The Stacktrace is also missing in 2.x. Do you have any idea what the problem could be? All these things worked perfectly fine under 1.x
When I open the "Extended Data" page I have a huge field named "_@error" which seems to have the missing stacktrace
Blake Niemyjski
@niemyjski
Can you paste a snippet of the code here
Everything is an event now and that could be the issue
Lukas Wöhrl
@woehrl01
saving is this step:

var error = e.ToExceptionless();

string path = Process.GetCurrentProcess().MainModule.FileName;

var version = FileVersionInfo.GetVersionInfo(path);

error.AddObject(version, "ExeVersion");

string errorAsString = JsonConvert.SerializeObject(error.Target);
var log = new ExceptionLogEntry
{
Log = errorAsString,
OccurenceTime = DateTime.Now
};
_dao.Create(log);

and the sending is doing this:
string log = _dao.First();
var error = JsonConvert.DeserializeObject<Error>(log);
var builder = new ErrorBuilder(error);
builder.Submit();
Blake Niemyjski
@niemyjski
Why not let us handle submission?
Where is dao writing these to?
Lukas Wöhrl
@woehrl01
the dao is storing them in the database
Blake Niemyjski
@niemyjski
And what determines when they are sent
Lukas Wöhrl
@woehrl01
the reason we can't use exceptionless directly are restrictions on the network. not every client is allowed to connect to the internet
so we have an agent which polls the database table end sends them
Blake Niemyjski
@niemyjski
Ah
So give me a few minutes (waking up)
Lukas Wöhrl
@woehrl01
take your time ;)
Blake Niemyjski
@niemyjski
But there's a much better way to do this now :)
Lukas Wöhrl
@woehrl01
by the way, another reason to do this, is that we can are also able to send exceptions which occure in c++. The agent assembls an exceptionless error from parsing a errorreport from a cpp library and sends those over the wire into exceptionless. (so no need to update the clients when we change the parsing ;) )
I know that all of this is easier with 2.x ;)