You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After putting the integration in place and updating the config file and definition file, we observe there are gaps in the data received.
We are running the query in System status event.
Whenever the as400 restarts over weekend, we observe that messageque event stops reporting data.
The fix for this mentioned in read as to delete the checkpoint file and restart the agent, but it happens after every server restart.
Description
NOTE: # Gaps in data for systemstatus event, the graph dips after every 1-2 mins, updated the definition file also. TIP: # ( Do NOT give us access or passwords to your New Relic account or API keys! )
Steps to Reproduce
NOTE: # Run the query : Select count(*) from AS400:SystemStatusEvent timeseries
Hi @shubhamnyaik@sschwartzman Any solution for the above issue, I am also facing the same where message queue data is coming on intermittent basis. Sometimes it is coming to NR after 2 days when compared the time of message queue events in AS400.
After putting the integration in place and updating the config file and definition file, we observe there are gaps in the data received.
We are running the query in System status event.
Whenever the as400 restarts over weekend, we observe that messageque event stops reporting data.
The fix for this mentioned in read as to delete the checkpoint file and restart the agent, but it happens after every server restart.
Description
NOTE: # Gaps in data for systemstatus event, the graph dips after every 1-2 mins, updated the definition file also.
TIP: # ( Do NOT give us access or passwords to your New Relic account or API keys! )
Steps to Reproduce
NOTE: # Run the query : Select count(*) from
AS400:SystemStatusEvent
timeseriesExpected Behavior
NOTE: # Smooth line with no data loss.
Relevant Logs / Console output
Your Environment
Additional context
The text was updated successfully, but these errors were encountered: