Hi guys
Installed agent on AIX with IIB on it
We can see PP but there is no DB statements in them as customer expected.
The IIB is using ODBC to connect the the sql server.
See below screenshot of the PP shows the Write to Tables that should be a DB statement
Is there any explanation for that?
Thanks in advance
Yos
Solved! Go to Solution.
Hello @Mikhail A.
It means Dynatrace SaaS/Managed also doesn't support similar to AppMon.
Do we have any road map for this?
Regards,
Babar
Good afternoon Makinov,
We are experiencing the same issue reported by Yosi_Neuman, one of our principal execution groups is connecting to multiple databases MSSQL and Oracle, but we are not able to see this calls on the pureptahs, we just catch exceptions if the flow presents an exception on a "store procedure " execution, it is a plus for the agent to bring this visibility as it is available for other technologies.
In this case we have 5 adapters that connect to databases and no traces to what they are doing. Check the image below.
Best regards
any recent addition to this pointer?
Hello rishabh_yadav2,
According to an answer from support, we should use the DatabaseNode instead of a ComputeNode on IBM Message Broker, this does not show a purepath with the database connection but you can see the query that is being called from the DatabaseNode, execution time and other related metrics.
Regards
Hey wmperez
That's the actual challenge that I am going through we have ComputeNode and post that I am failing to get the DB Queries.
Good morning,
One of the product managers explain this when we report this issue "We support monitoring of DatabaseRetrieve and DatabaseRoute nodes, but unfortunately we currently cannot trace generic database calls that are triggered inside ComputeNodes", this means you will have to change your code to achieve this visibility.
Basically what you will get is the SQL statement and performance metrics about this SQL statement...
Best regards
Hello
Is there any news on this.
Im facing the same need now and I cant retrieve any DB call.
What workaround did you made ?