[ZBX-7593] zabbix server (DM setup) can genarate IDs which do not correspond specification Created: 2013 Dec 27 Updated: 2017 May 30 Resolved: 2013 Dec 28 |
|
Status: | Closed |
Project: | ZABBIX BUGS AND ISSUES |
Component/s: | Server (S) |
Affects Version/s: | 2.0.10, 2.2.1 |
Fix Version/s: | None |
Type: | Incident report | Priority: | Minor |
Reporter: | Oleksii Zagorskyi | Assignee: | Unassigned |
Resolution: | Won't fix | Votes: | 0 |
Labels: | dm | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Description |
In case if we convert a clean db (just created and filled by config data) to DM mode and start to use it then server generates IDs like 100000000000001 in tables events, alerts and may be other. Note first part "1000" which should be "1001" for NodeID=1 according to specification https://www.zabbix.com/documentation/2.2/manual/appendix/faq Of course it's not critical, but it can mislead in case of troubleshooting and investigation some mysterious problems. I'm not sure what we have to do with this. |
Comments |
Comment by Oleksii Zagorskyi [ 2013 Dec 27 ] |
For example issues where we can see such IDs: |
Comment by Alexander Vladishev [ 2013 Dec 28 ] |
Ids like nnncccxxxxxxxxxxxxx used only for configuration tables like items, hosts etc. For historical data used ids like nnnxxxxxxxxxxxxxxxx. It's not a bug. I'm closing the issue. |
Comment by Oleksii Zagorskyi [ 2013 Dec 28 ] |
Thanks Aleksander. Such a detail is not documented, unfortunately Actually the picture is not consistent - it depends when database has been converted to DM. |
Comment by Oleksii Zagorskyi [ 2014 Feb 07 ] |
These details added on https://www.zabbix.com/documentation/2.2/manual/appendix/faq |