testing the new APMSQL capability of CA APM.
As you can see from the attached image I can see only agents under "Custom Metric Host (Virtual)".
No visibility and access to all my deployed agents.
I configured the APMSQL to point the MOM of my cluster environment.
APMSQL is not an agent, but an JDBC interface to pull data from SmartStor.
My bad; did not see the attachment there showing your query.
This is the query I done:
selectagent_nameFROM numerical_metric_dataWHEREfrequency =15000AND ts > '2017-05-11 13:00:00.0'GROUP BY agent_nameORDER By agent_name
This is the output:
agent_nameCEM2ProduzioneCustom Business Application Agent (Virtual)Custom Metric Agent (Virtual)DURC-PDDSM2Portale
the query Sows only the agents reported under MOM.
The date range ts > '2017-5-11 13:00' is a small range. Would you get more result if you expand the date range?
I ran this with the same result:
selectagent_nameFROM numerical_metric_dataWHEREfrequency =15000AND ts > '2017-05-08 13:00:00.0'GROUP BY agent_nameORDER By agent_name
and the output is the same:
instead the investigator shows all the agents:
As Francis stated, 5/11 @ 13:00 is a small range. Can you try a day before?
I ran the same query that you did and got some data back. Also check your Investigator and see if all the Collectors are reporting. That is where the data will come from.
The investigator shows all the agents:
I had this issue when I ran this as myself, but when I ran this as the admin it worked for me. I haven't had time to look to see why my credentials didn't work before, but they should have, since my LDAP userid has the same rights. Hope that helps.
I think I have the same issue, my user is an LDAP user with ADMIN rights. Sholud I try using admin.
how can I enable the admin user to login even if I have enables CA EEM ?
It is a local account for us, since we don't use CA EEM.
You can use local admin by doing the following on the MOM.
1. Modify realms.xml and above the LDAP section, enter this:
<realm descriptor="Local Users and Groups Realm" id="Local Users and Groups" active="true"> <property name="usersFile"> <value>users.xml</value> </property> </realm>
2. Save and exit and in users.xml, make sure you have this. Save and exit that file and restart MOM.
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <principals xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="0.3" plainTextPasswords="false" xsi:noNamespaceSchemaLocation="users0.3.xsd"> <users> <user password="" name="SaasAdmin"/> <user password="" name="Admin"/> </users> <groups> <group name="CEM Analyst" description="CEM Analyst Group"/> <group name="CEM System Administrator" description="CEM System Administrator Group"> <user name="Admin"/> <user name="cemadmin"/> </group> <group name="Admin" description="Administrator Group"> <user name="Admin"/> <user name="cemadmin"/> </group> <group name="CEM Tenant Administrator" description="CEM Tenant Administrator Group"> <user name="SaasAdmin"/> </group> <group name="CEM Configuration Administrator" description="CEM Configuration Administrator Group"/> <group name="CEM Incident Analyst" description="CEM Incident Analyst Group"/> </groups></principals>
Your suggestion works, I added the new realm on users.xml file and I'm able to login with local and ldap users.
Now I've a new question about the APMSQL tools:
I created a new user to run APMSQL query, adding the following lines in the configuration file, but it continue to see only the agent "Custom Metric Host (Virtual)".
I'm able to see all the agents from queries, only when using the local admin user. Any hint?
<group name="APMSQL" description="APMSQL users Group"> <user name="ususi01"/>
added this line on every domain section:
<grant group="APMSQL" permission="read" />
<grant group="APMSQL" permission="full" />
For testing purpose, could you make the user "ususi01" part of APM Admin Group.
Restart EM and APMSQL Server.
Connect to APMSQL server using "ususi01"
Test the connection too
And try the query and see....
Also, when you say "I'm able to see all the agents from queries, only when using the local admin user"
can you see the Agents in all Domains (SuperDomain and SubDomains)?
Hello the problem was because the file users.xml file was not copied on all the EM collectors.
I have dynamic domains:
but it doesn't sync the user.xml just the domain.xml, so I copied the users.xml on all the EM and now the user is able to see also the metrics on agents registered on collectors.
With Matt's response , marking as answered since it is a clear next step.
If Matt's response does not solve the issue, please open a case to pursue further. Then please post the resolution of the case to help others that may have this situation.
You may also post follow-up questions as needed
We were able to create a java wrapper that uses the TEAM Center API token mechanism which works well, but we are finding this same issue. We can only grab the data from the MOM and not from the other collectors.
Will this be fixed in later versions, since we don't want to use the admin account and/or a local user.xml account to pull data.
I submitted a case for this as well, since maybe it is a permissions issue....I will update this based on the case or vise versa.
We had this same issue. Only the local "Admin" account was able to query data from all of the EMs. Users defined within LDAP were not able to see data from any of the Collectors. But adding the LDAP configuration information within the realms.xml file and modifying domains.xml to allow some LDAP groups to access those domains on all of the collectors resolved the issue.
I found the following query to be very helpful in troubleshooting this problem. It gives a list of all EMs which can be queried by the credentials used to connect to APMSQL. This query will only return EMs which have metrics over the past minute....you can increase that by changing "-1" to a bigger number like "-5".
SELECT source_nameFROM numerical_metric_dataWHERE frequency = 15000AND ts > TIMESTAMPADD(SQL_TSI_MINUTE, -1, NOW())GROUP BY source_nameORDER By source_name
Domain replication should have taken care of this problem automatically for you (unless you've disabled it).
As for realms.xml, that is local to each EM, so I could see how that might prevent a token from flowing from MOM to collector. Sounds like this needs to be addressed as a defect.